Processes are not running in version 2025.0.166

[tolgademir]

Hello,

In version 2025.0.166, when our processes are triggered or manually triggered via orchestrator, they get the error in the image and fall into the faulted state. I saw many topics in the forum, I think there is a technical problem caused by the relevant version.

I have some findings related to this error.

1. Local processes can work without any problems.

2. After a new publish, the processes fall into the faulted state directly.

Other issues I’ve seen;

Some processes not working from assistant after 2025.0.166 STS update

I am using UiPath Community Edition. Processes were working fine before the 2025.0.166 STS update. These processes work fine when run from studio but fail when run from assistant via triggers. They give “Could not find the user-interface (UI) element for this action”. I tried updating to latest package versions, deploying new build but no use. Note: processes are working fine when run from studio.

All Processes Faulted After Update to Studio 2025.0.166

Hello, After updating to UiPath Studio version 2025.0.166, all of our processes have suddenly gone into a faulted state. When I check the Details of any of the failed processes, I receive the following error message: Raw message: The Client ID or Client Secret is incorrect. in Main.xaml at RaiseAlert “Raise Alert” at Sequence “Sequence” at TryCatch “Try initializing settings and applications” at InternalState “Initialization” at StateMachine “Arch” at DynamicActivity “Main” UiPath.Core…

How can I find a solution to this error?

Thank you.

[ganesh5 (Ganesh)]

I am also facing same issue after recent update. Also my code stops running on unattended mode which was running fine on previous version.

[prashant1603765 (Prashant Kumar)]

Hi @tolgademir

Please try to disconnect the assistant and reconnect with orchestrator.
If not working try to remove machine and create again same and connect with machine key or client ID and client secret .

Happy Automation!

[singh_sumit (Sumit Singh Tariyal)]

Hey @tolgademir many of the fellow member are facing that type of problem.as per the solution is go to orchestrator remove the machine and add that same machine again that it will generate client ID and client Secret copy that and paste it to the assistant where are you running your unattended bot.noww your are good to go to run your process again.

cheers

[ganesh5 (Ganesh)]

This issue can be solved if you use Client id in Connection type instead of machine key while connecting UiPath a/c from assistance on orchestrator setting.

[ashokkarale]

Hey @loginerror,

Can we have a Knowledgebase on this?
What’s the root cause and a fixed solution from product side.

[tolgademir]

Hello all, I was experiencing the same issue in an instance using the latest version of Studio. I solved the issue by upgrading the Studio version to version 23.10 in both the live and development environments. As far as I understand, there is a critical bug in the new Studio version. Thanks for all your help.

[loginerror (Maciej Kuźmicz)]

I took the liberty to remove the solution tag from your post, given that we fixed the issue and the 25.0.166 should now work correctly after a small update.