i can’t run any job suddenly i have not done any update the assistant is connected normally the license is active but i keep getting this
Please check your assets which are using in this process. As per your screenshot, bot is unable to load your asset. might be assets not linked or different locations.
Happy Automation
all is linked correctly if i run the same process from the UiPath assistant i work fine also nothing has changed this suddenly appeared
Hey @mohamed.saty2012 The Robot is trying to access an Orchestrator asset or a resource that uses OAuth2 authentication (like a cloud API), and the machine running the job via Orchestrator cannot retrieve the required credentials (Client ID/Secret) — either because the credentials are expired, missing, or because the robot is running under a different identity in unattended mode.
cheers
Might be not have asset access, not be configured to run unattended (check robot settings).
Be in the wrong Orchestrator folder or Machine template. pls check in Orchestrator > Tenant > Robots and ensure:
myrobot-unattended is assigned to the right machine and folder.
Happy Automation
how do i know that the password has been expired
I saw another user report this elsewhere today, so weird coincidence, maybe something got broken.
They indicated it was fixed by making a new machine template ID and secret key and linking again.
It seems your robot machine connected to the orchestrator there are some communication issues. Try creating the new machine template and get the client ID and Client secret using that connect your robot machine with orchestrator.
Could you please try to reconnect the assistant and try.
Hey. I got the same error for every project that has been started from Orchestrator on my Community Cloud since yesterdays’ evening.
I confirmed from assistant that there’s a valid connection to Orchestrator from my unattended machine and Orchestrator Monitoring / Machines I saw machine was connected. I was able to run same automation that failed from Studio on unattended machine without issues.
What I did to fix this: removed old machine, created new machine template and connected from unattended machine using client id / secret.
thanks, i will try this and feed you back
@mohamed.saty2012 if you are using for example sharepoint or any activity .where you are (Client ID/Secret) they might be delete from azure portal. and if you are not using any API then .this might be machine template issues. so for machine try to setup(add) that machine again then it will generate (Client ID/Secret) and then pass it to the assistant where you running the process.
cheers
this actualy worked thanks for your support Brother
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
