Failure to start Orchestrator RPA job in maestro

Help Maestro
1

Hi everyone,

I’m currently building an agentic automation solution using UiPath Maestro + Web Studio and I’m facing an issue with solution deployment/debugging.

Setup:

  • Created a new Solution directly from Maestro using “Start Modeling”
  • Added a BPMN process
  • Added RPA workflows inside the same solution
  • Using “Deploy resources before debugging”

Problem:

  • Local workflow debugging works normally
  • But running the BPMN process fails
  • Initially I got:
    “Failure to start Orchestrator RPA job”
  • Then after enabling “Deploy resources before debugging”, deployment started hanging on:
    designer.solution_debug.publish_queued

I later discovered a package version conflict:
1.0.0 version already exists for this package

After incrementing the version, publishing started but now fails with:

Failed to provision solution projects due to timeout

Full error:
Failed to provision solution projects due to timeout

Questions:

  1. Is this a known Maestro/Web Studio provisioning issue?
  2. Does Maestro internally require Orchestrator resources/processes even if everything is created only from the Solution view?
  3. Is there a recommended way to force-refresh/rebuild orchestration bindings for solution workflows?
  4. Could this be caused by corrupted solution metadata?
  5. Are there any tenant/folder/licensing requirements specific to Maestro solutions that are easy to miss?

Additional notes:

  • I recreated the solution from scratch and still see the same issue
  • Simple workflows like “Log Message” also fail during deployment
  • I’m using UiPath Automation Cloud + Maestro Web Studio

Any guidance would be appreciated because I’m currently stuck understanding whether this is:

but i didn’t understand any of the given solutions i didn’t know how to apply them

Thanks!

2

@ziyad_tarek

It looks like a issue from platform itself in new community version

I tried the same on community and a different cloud version and it did work on others and not not on community

@loginerror looks like the issue is with community version as projects are not getting deployed with multiple errors if we see the networks tab…

Cheers

3

But i have the enterprise trial licence i am not using the community version

4

@ziyad_tarek

Enterprise trail activated from comunity also follows same type

Cheers

5

->Verify Robot, Machine Template, and Runtime are connected correctly in the target folder
->Check if the solution was successfully published to Orchestrator or not
->Open browser DevTools → Network/Console while debugging to capture hidden provisioning errors
->Redeploy by removing the older packages/versions from orchestrator

Maestro solutions still depend on Orchestrator resources internally for job execution, so missing runtime/folder mappings can cause Failure to start Orchestrator RPA job

6

@ziyad_tarek

You can check now looks like its resolved

Cheers

8

Hei @ziyad_tarek,
This is likely related to a incident we had recently on our community scaleunit, details here: UiPath Status - Intermittent disruptions to few features in Community region.
It was swiftly resolved and you shouldn’t experience the above issue any longer, if this is not the case please let us know.
Thanks, Alex.