Get Credential: Status code: 409 (Conflict). Orchestrator response:
Failed to read XXXX from Credential Store type XXXX (read only) Error code: 2304
Why would someone get this error from Studio and not me getting the same credential?
Get Credential: Status code: 409 (Conflict). Orchestrator response:
Failed to read XXXX from Credential Store type XXXX (read only) Error code: 2304
Why would someone get this error from Studio and not me getting the same credential?
This error usually means the issue is not with the asset itself, but with how that specific user/robot/runtime is accessing the external credential store.
Error 2304 is thrown by Orchestrator when it cannot retrieve the credential from the connected secure store (CyberArk, Azure Key Vault, etc.), even though the asset exists.
Refer this KB:
Hi @adext
adding to Ashok’s answer on error 2304, the part that explains the “why me and not them” is usually permissions inside the external vault itself, not Orchestrator
when Orchestrator is connected to something like CyberArk or Azure Key Vault, its not Orchestrator deciding who can read the secret, its the vault. The credential store usually maps access down to the actual runtime identity, either the robot account or the service account tied to that specific machine/session, and grants read access to that secret in the vault only to certain accounts or AD groups. So if your robot runs under an identity that has access to that safe/vault and someone else’s runs under a different identity that doesnt, you would get 409/2304 while they dont, or the other way around
worth checking with whoever manages the CyberArk/Key Vault side directly, ask them to confirm wich identity your robot/session used at the time of the error and whether that identity has read permission on that specific secret. Comparing that against a working case is usually faster than digging on the UiPath side, since orchestrator is just relaying the vaults rejection
hope this helps narrow it down ![]()
I’d compare the exact tenant, folder, asset and any per-account/machine overrides first. The same asset name can resolve differently for two users, including a different external secret name.
Also, the vault identity depends on the credential-store configuration. For example, Azure Key Vault commonly uses the store’s configured application/service principal, not each Studio user’s Windows identity. Check the vault audit log for the actual caller and secret requested before changing permissions. Which credential-store provider are you using?
I have similar issue with Azure Key Vault. Connection is setup on two tenants with the same Azure app. On one tenant get credential is working, on the other not.