Autopilot Error While Building Escalation App in Agentic Automation Course

Hi everyone,

I’m currently following the Agentic Automation training module specifically the lesson “Build an escalation app for your agent.”

While trying to create the escalation app (after configuring the Action Schema), I’m getting this error message:

“We’re currently facing an issue with the Autopilot service which is preventing us from processing your request. Please try again later, or contact your administrator for further assistance.”

Trace Id: d3b17331cb9d4c649099092f7b21bc68

Even when I try to manually create an app by going to Apps → Create App (without using Autopilot), I still receive an error saying:

“App addition is in progress. Please check after some time.”

It looks like the page creation or Autopilot process fails at the backend.

I’ve already tried:

  • Logging out and logging back in
  • Clearing cache and cookies
  • Trying a different browser (Chrome and Edge, also in Incognito mode)
  • Creating a new solution from scratch

But the issue persists.

Could this be related to any tenant/organization-level configuration, region-specific outage, or permission setting?
For example:

Do I need to enable any specific Autopilot or App service capability in my organization settings?
Is there any dependency on Action Center licensing or folder permissions for this step?
Or is this a known temporary issue in the cloud environment?

Any guidance or workaround would be appreciated


Hi, @Zehra

Check with your UiPath admin to ensure you have permission for Apps and Autopilot in the right folder, and that App/Action Center services are enabled for your tenant. If everything looks correct, check https://status.uipath.com for current outages—these errors often occur with backend or permission issues

1 Like

@Zehra

Welcome to the community

First try to open the inspect window in browser..go to networks tab and then check whcih request is failing when creating the app..that might shed some light on the issue and we can move further from there

Cheers

1 Like

Thanks everyone for the support!
It turns out the issue was related to my account settings

1 Like