One of the RPA projects is triggering the Agent. I was able to run the project with the Debug on Cloud option until a few hours earlier. Now it throws an error on the provisioning:
2025-09-23 17:38:28.280 GMT+3: Error: Request failed with status 500: {“message”:“An error has occurred.”,“errorCode”:0,“traceId”:“00-e05d751cb8544a99970582da7c00b7ed-094a9fb236fe1898-00”}
I also started encountering API errors in our enterprise-licensed account, which were resolved with a service ticket. The UI and the way we manage the tools, context is changing but we would enjoy a stable product.
Best regards
one new error message:
2025-09-23 18:16:56.066 GMT+3: Error: Errors from: orchestrator.uipath.com
• Process ‘CustomerServiceAgent’: Error code - 1677, Message - ‘This process’s package is not available anymore. Changes are not possible.’
But the Customer Service Agent is available in the Solution:
As per my understanding this error occurs when the package version linked to the process is no longer available in Orchestrator. Go to Orchestrator → Processes, check the CustomerServiceAgent process, and update it to point to the latest package version published in Packages. After updating, republish the project from Studio if needed and refresh the Solution in Agent Builder—this resolves the resource provisioning failure.
I tried this but it didn’t solve. So when I use solutions “folder” and call any project or agent inside that solution, it creates another package as projectName_1 or _2 in the orchestrator. Maybe my first mistake was deleting these _1 _2 projects from the process section. But when I call the agent from the RPA workflow it created _1 one again.
This is the main reason why I don’t like to use one solution to store all projects inside. I usually keep all of them separately then use maestro to integrate. But this one was a small demo so I started this way. Anyways.
In the original project (agent) CustomerServiceAgent the version part looks like this:
@sarikayaebru ,
Publish each automation project to Orchestrator as a separate package, ensure unique names and proper versioning, and remove duplicates by cleaning up _1 or _2 suffixed processes before republishing to prevent conflicts and maintain clarity in deployment
I wanted to use the Solutions properly instead of having each process separately. I keep this as plan B and will wait for a while for a different input.
If this is not how the solutions used and what for, why we have solution folder?
And to divide them, I need to create them again from scratch.
When you click on debug it would show you another screen…intermittent not sure of thsat is removed but there if old references are present try to remove them
There isn’t such a screen, only the one appears to ask for the input and then the debug starts.
I deleted all old packages from Orchestrator, uninstalled solution and deleted the folders. Even when I uninstall the solution deployment it shows as deployed in the studio screen.
Now the error message has changed and it fails to create Debug Folder in “My Workspace”. I think the solution and the backend for that are completely broken.
By the way, I can debug it from Studio desktop, and the process is running when I trigger it from an app. Only the debugging in Studio Web is not working.
