Robot has no credentials

How do I assign credentials to a robot?

I have a process I set up previously that worked fine. Today I came to run it and orchestrator says the process can’t run because the robot has no credentials defined. There doesn’t seem to be any menu option in the robots list, and I can’t find anyway to assign credentials to a robot. Any help?

Hi @Nick_Scott ,
Please check these once:

  1. Go to Orchestrator → Assets.
  2. Verify that the required Credential Asset exists and contains a valid username/password.
  3. Ensure the robot’s folder has access to that asset.
  4. Check the process configuration and confirm it references the correct credential asset name.
  5. If the asset was deleted, renamed, or permissions changed, update it and run the job again.

Thanks

Hi @Nick_Scott,

In modern folders, credentials aren’t set from the Robots list. They’re set on the user or robot account the robot runs as.

In Orchestrator, go to Tenant → Manage Access → Assign roles, find the user or robot account, and choose “Edit”. Under Unattended setup, select custom Windows credentials and enter the machine’s “DOMAIN\username” and password, then update. Make sure that account is assigned to the folder that contains the process.

Most likely the Windows password has recently changed or expired, or the credentials were cleared.

Hope this helps.

Cheers!

Hi @Nick_Scott,

In modern folders, the first thing I would check is the unattended setup for the account running the process.

Go to Orchestrator → Tenant → Manage Access, find the relevant user or robot account, and check its Unattended setup. If the process requires an unattended Windows session, verify that the correct Windows username and password are configured and that the account is assigned to the appropriate folder.

A Credential Asset is different: it stores credentials that a workflow can retrieve at runtime, for example, to log in to an application. Creating one does not automatically configure the Windows credentials required to start an unattended job.

Since the process worked previously, also check whether the Windows password changed or expired, or whether the unattended setup was modified.

If the credentials are configured correctly, check the job error details and the account’s folder and machine assignments to narrow down the cause.

Hi guys, and thanks for your responses.

It turns out I already had a robot assigned to the credentials I was trying to use, so I just had to link it to the folder I was trying to use.

Hi @Nick_Scott ,

Just to clarify, a Credential Asset is used to store credentials that a workflow needs, whereas unattended Windows credentials are configured in the account’s Unattended setup in Orchestrator.

If the error says the robot has no credentials defined, check the Unattended setup first and verify that the correct Windows credentials are configured for the account running the process.

Hope this helps!

oh that’s interesting … when I setup a robot, but can I get back to the unattended setup page, to edit it? where is it?

Hi @Nick_Scott,

Yes, you can edit it later.

Go to Orchestrator → Tenant → Manage Access, find the user account, click Edit, and look for the Unattended setup section. From there, you can update the Windows credentials if you have the required permissions.

The exact options may vary depending on your Orchestrator version and account setup.

If this helps, please consider marking the reply as the solution. Hope it helps!

Go to the Orchestrator > Tenant > Manage Access > Access Rule > Robot account, find the account , and Edit

Then you can update the Robot account credentials for unattended execution.

Thanks!

ah there it is thanks, again, I’ve been looking for that. All I could find was a list with a shield icon at the end of the row with like access permissions.

I think you were on the Robots tab, where you can manage robot permissions, such as what the robot can access.

If your issue has been resolved, please mark the answer as the solution.