Agent Prod Runtime Details

I currently Have an agent in Prod and setup to run in Assistant. When I run it in Assitant It picks up an account available in that folder however the prompt fails consistently.

But when I run the same Agent in Orchestrator manually, it picks up my personal account (My name) and runs successfully.

Is there a way to use the identiy of the user logged into assistant instead of picking up random accounts?

Is there a way to configure the Agent to ONLY pick up a users account when running in Assistant?


^^In this image, the assistant throws an error due to the identity.


^^In this example, it takes my identity and runs successfully.

Hi, @ashton.lalchan

This is expected behavior.

Agents run from UiPath Assistant use the robot/folder identity, not the logged-in user, so they may pick any available account in the folder. There is no way to force Assistant to use the user’s identity.

Make the Agent user-independent by resolving the process using Process Name / Process ID / Use Case ID, not the executing user. This ensures it works the same from Assistant and Orchestrator.

@ashton.lalchan

try to go to orchestrator folder → edit the process → Go to package requirements and see if its asking for user selection

If yes you can select there

cheers

hi @Anil_G
Agents dont have that option when going to package requirements.

Hi @arjun.shiroya can you clarify what you mean by this?

Hi @ashton.lalchan ,

The problem is that you are trying to run an API workflow, which only runs in Serverless Robots and they do not support any particular user identity or credential to run, they just require an unattended account to run the process. So they pick up any available unattended account unless specified like in your case - Running using your account from Orchestrator.

Some of the solutions for this are-

  1. Remove other accounts from the process folder and just keep yours.
  2. Or you can use the Account- Machine mapping feature of UiPath to specify a particular account to be used for a machine template. So whenever the process runs using the machine template, it prefers that account only.

For more info on how to configure Account- Machine mapping, please refer to this- https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/configuring-account-machine-mappings#configuring-account-machine-mappings