[Agent Builder] Document Validation Task fails with OrchestratorFolderNotFoundError — only in a shared team folder, not in personal workspace

Help Agent Builder
1

I have an Agent (Maestro BPMN + Agent Builder, “Document Extraction Agent”) that uses an IXP tool for extraction and a Document Validation Task escalation (Document Validation Station) for human review. It runs end-to-end successfully in my personal workspace folder. When deployed and run in a shared team folder, everything works identically right up until the validation step, which fails every single time with OrchestratorFolderNotFoundError. Environment

  • Automation Cloud, Agent Builder (LowCode agent type)
  • Package: Referral.Management.agent.Document.Extraction.Agent, version 1.0.5
  • Escalation resource type: AgentIxpVsEscalationResourceConfig, escalation type Document Validation Task (Document Validation Station)
  • Extraction resource type: AgentIxpExtractionResourceConfig
  • Runtime: Cloud Robot - Serverless
  • Process: Maestro BPMN {
    “code”: “AGENT_RUNTIME.UNEXPECTED_ERROR”,
    “message”: “Failure in the Orchestrator Job”,
    “detail”: “An unexpected error occurred during agent execution, please try again later or contact your Administrator.\nError Details:\nOperation failed with status: Failed, error: {‘message’: ‘Orchestrator folder does not exist.’, ‘severity’: ‘Error’, ‘code’: ‘[OrchestratorFolderNotFoundError]’, ‘parameters’: }”,
    “category”: “System”,
    “status”: 502
    } Checked all related access to cloud serverless bot it has all action create edit and view
2

Hi @VarunMGhanekar

since it works in your personal workspace but fails in the shared folder specifically at the validation step, it looks like a folder/resource configuration issue.

I would check that the Document Validation Task/escalation resource is created and configured in the shared folder and that the process has access to that folder.

If it was created in the personal workspace, try recreating/redeploying the escalation resource in the shared folder.

3

Hi @VarunMGhanekar ,
This usually indicates a folder context mismatch, not a permissions issue.

Since the agent works in your personal workspace but fails in the shared team folder exactly when creating the Document Validation Task, UiPath is likely trying to create the validation action in a folder that the validation service cannot resolve.

You can check these once:

  1. Document Validation Station configuration

    • Open the escalation configuration and recreate/reselect the Document Validation Task resource after moving to the shared folder.
    • Ensure it is published and available in the same folder where the process runs.

  2. Folder assignment

    • Verify the Agent, Process, Action Center/Validation resources, and Document Understanding resources all belong to the same shared folder.
    • If any resource still references your personal workspace folder ID, the validation step will fail with OrchestratorFolderNotFoundError.

  3. Serverless Robot permissions

    • Besides Action permissions, ensure the serverless runtime identity has access to:
      • View Folder
      • Use Folder
      • Create Actions/Tasks
      • Document Understanding resources
    • Confirm permissions are granted directly in the shared folder.

  4. Recreate the escalation resource

    • Delete and recreate the AgentIxpVsEscalationResourceConfig in the shared folder.
    • Republish the agent/package and test again.

  5. Check folder path references

    • Review any folder names, folder IDs, environment variables, or resource references hardcoded during development in your personal workspace.

Thanks