Manual job launch fails with "Unknown identity" after upgrading to 2026.2.0

Hello,

After upgrading from 2026.1.6 to 2026.2.0, a domain user can no longer start a script manually from the admin console. The job fails immediately with Failed to start script. Unknown identity: DOMAIN\Account

I did some troubleshooting before posting here and I found out that the console identifies me as DOMAIN\Account (with domain name in uppercase), and automatically creates an identity for me that I can find under Security > Identities. This automatically generated identity is stored as domain\account (With domain in lowercase).
I manually created a second identity for my account with domain name in uppercase, and I was able to start a job successfully.

Here are some details about my environment :

Version: 2026.2.0
Auth: Windows Authentication, AD domain account
Database: PostgreSQL
Licensed: Yes
Install: As a Windows Service with SYSTEM account

Thank you in advance for your help.