GetApplicationCredential returns appCredentialNotFound in Zurich despite complete credential config
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hello,
I am troubleshooting the GetApplicationCredential component in ServiceNow Zurich RPA Hub. It consistently fails with:
appCredentialNotFound: Application Credential not found
To eliminate issues with the existing automation, I created a completely isolated test containing only:
START
→ GetApplicationCredential
→ END
The test uses brand-new records created specifically for troubleshooting.
Environment
ServiceNow release: Zurich
Desktop Design Studio: 10.0.1
Unattended Robot: 11.2.0
Login Agent: 3.1.0
Process type: Unattended
DDS and the Unattended Robot are installed on the same Windows VM. The ServiceNow instance/RPA Hub Workspace is accessed through a browser from another computer.
Clean test configuration
1. Created a new Business Application with a unique name.
2. Created a new Application Credential:
- Active = true
- External Credential = false
- Application Name references the new Business Application
- Username and password are populated
- Domain = global
3. Added the new Application Credential to the existing Credential Group.
4. The Credential Group also contains the working Windows Robot Credential.
5. Added the new Business Application to the clean Bot Process.
6. Created a Process Credential Mapping:
- Correct Credential Group
- Correct Bot Process
- Authorized user added
- Shared = false
7. Assigned the existing connected Unattended Robot to the process.
8. Created the Process Robot Credential using:
- The same Credential Group
- The same robot
- The clean Bot Process
9. Assigned the DDS project to the clean Bot Process.
10. Configured GetApplicationCredential.Name to exactly match the Business Application name.
11. Connected both required outputs:
- UserName to a String variable
- Password to a SecureString variable
12. Published a new package version and confirmed the clean Bot Process ran that exact version.
Verification already completed
- The Application Credential and Bot Process reference the exact same Business Application sys_id.
- The CMDB relationship is Uses::Used by.
- Application Credential domain = global.
- Credential Group domain = global.
- Bot Process domain = global.
- The robot service account has the RPA robot role.
- The robot successfully receives jobs and starts the Windows session.
- The correct process, robot, package, and package version are shown in runtime and service logs.
- The runtime versions exactly match the installers currently downloaded from the Zurich instance.
- A new Business Application, Application Credential, package, DDS project, and Bot Process were all used.
- No credential values are displayed or logged.
Results
Running locally from DDS fails at GetApplicationCredential with:
Component 'GetApplicationCredential' failed to execute in the activity 'Main'.
Exception has been thrown by the target of an invocation.
appCredentialNotFound: Application Credential not found
Running the published package through RPA Hub on the Unattended Robot produces the exact same failure.
The runtime and unattended service logs confirm that the correct robot, process, and package are launched, but they do not provide any additional credential lookup details.
Questions
Is there another required record, permission, property, relationship, or backend configuration that GetApplicationCredential depends on but is not visible in RPA Hub Workspace?
Does GetApplicationCredential search by the Business Application name, Application Credential name, Business Application sys_id, or another internal value?
Are there any known Zurich defects involving GetApplicationCredential returning appCredentialNotFound even when the complete credential chain is configured?
Is there a server-side log, API endpoint, script, or table query that can show why the Application Credential lookup returns no result?
Any guidance on the next diagnostic step would be appreciated.