Extract Document Data activity fails to authenticate with a different tenant ML Project using Design Time External Connection in modern DU projects

News Knowledge Base
1

Extract Document Data activity fails to authenticate with a different tenant ML Project using Design Time External Connection in Modern DU projects.

Issue Description

Extract Document Data activity fails to authenticate with a different tenant ML Project using Design Time External Connection in Modern DU projects.

The connection is successfully established using "Design Time External Connection," but the process encounters the following error upon execution.

Extract Document Data: The resource requested on `StartDigitization` cannot be found. CF-RAY: XXXXXXXXXXXXXX-DFW. AppId: cid-v1:xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx.

Root Cause

The Runtime Tenant URL is set to null (i.e., ""), and the Runtime Credentials Asset remains empty in the "Extract Document Data" properties. If the Runtime configurations are not set, the activity attempts to connect to the environment of the Robot, which results in failure when the associated ML project is located in a different Orchestrator or tenant.

kb-0EMPa00000Lxly6.png303×506 30.2 KB

Resolution

  1. Configure the "Runtime Credentials Asset" and "Runtime Tenant URL."

    • Create a Credential Asset in the Orchestrator where the Robot is connected.
    • Set the Username in the Credential Asset as the "Client ID" of the External Application.
    • Set the Password in the Credential Asset as the "Client Secret" of the External Application.
    • Configure the "Runtime Tenant URL" with the URL of the External Application.

  2. Format the Runtime Tenant URL in the following manner:

    https://<baseURL>/<OrganizationName>/<TenantName>

  3. Refer to the official documentation for detailed instructions: Configuring External Connection

Why is the Runtime Configuration necessary?

Runtime configurations allow the execution of Document Understanding activities using resources from external projects or tenants. These settings are not stored in workflows and must be explicitly configured for runtime execution.

Runtime external connections are required regardless of the mode (Unattended, Debug, Studio, or Assistant).

Also, a similar error is observed when moving Document Understanding™ modern projects between tenants or organizations

Contact UiPath Product Support

If the issue persists, create a UiPath Support Ticket and provide the following details:

  • Studio Version.
  • UiPath.DocumentUnderstanding.Activities Version.
  • URLs or links to any referenced documentation.