While running agent builder i am facing the provision resource timeout
even though I have enterprise trial edition.
Hi,
Please activate Stander Trial.
Hi @Joswa_Dsouza4 ,
This usually happens when the Standard Trial isn’t activated properly, even if you’re on Enterprise Trial.
Go to Admin > Licenses and make sure the Standard Trial is active. If not, click Start Trial.
If it’s still not working, reach out to UiPath Support — they might need to provision resources manually.
Thanks for your solution will check on this ![]()
Let me know if you need further assistance
Still Getting Same Issue
Can you please share the error details
Hi @Joswa_Dsouza4 , can you please try the below 4 points
- In Agent Builder → Tools → Processes, remove the broken processes and add them again from the correct folder/tenant.
- Ensure the processes are published and available in Orchestrator.
- Your user needs Processes.View, Packages.View (and folder access).
- Log out/in to the same org/tenant and republish.
Thank you for your solution, Issue Resolved
Thank you please mark as solution
I am facing an issue while adding an escalation to my Agent in UiPath Automation Cloud (Action Center). The agent works fine without escalation, but when I include an escalation step linked to an Action App, the solution fails to provision.
Below are the details:
- Error Message:
Failed to provision solution resources due to timeout - Timestamp: 2025-11-12 16:24:09.152 GMT+5:30
- Observed Behavior:
- The agent deploys and runs correctly without escalation.
- When an escalation (Action App) is added, the publishing process fails [file:///C:/Users/saket/OneDrive/Pictures/Screenshots/Screenshot%202025-11-12%20163905.png](file:///C:/Users/saket/OneDrive/Pictures/Screenshots/Screenshot%202025-11-12%20163905.png)
with the above timeout error.
- Action App Name: SimpleApprovalApp
- Agent Name: GreetUser
- Steps Already Tried:
- Republished the app and redeployed the agent
- Checked all input/output mappings
- Reconnected to Orchestrator
Please assist in identifying the root cause or any configuration limits that could be causing this provisioning timeout.
I have also attached a screenshot showing the exact error and setup for your reference.


