Hi UiPath team,
While debugging a Maestro BPMN solution in Studio Web, a service task that starts a referenced API Workflow failed with:
170007 — The job’s associated process could not be found
The error identifies the failure type, but does not provide enough resolved dependency context to diagnose or repair it from the runtime view.
Steps to reproduce
- Create a Solution with a Maestro BPMN process that references an API Workflow.
- Deploy/debug the Solution in Studio Web.
- Run the BPMN process when the referenced workflow is missing, misbound, unavailable in the target folder, or not resolved correctly.
- Open the failed BPMN incident.
Actual result
The BPMN activity fails with error 170007. The incident does not show the resolved process/resource key, target folder, expected package/version, deployment state, child-job link, or suggested repair action. Developers must manually inspect Studio Web, Solutions, Maestro, and Orchestrator.
Expected result
The failed BPMN activity should show:
- Referenced process and resource key
- Resolved tenant, folder, package, and version
- Whether a child job was created
- Correlation ID and direct link to the child job/process
- Clear remediation, such as deploy, rebind, fix permissions, or select a valid version
Impact
For multi-project solutions, this turns a diagnosable dependency issue into a cross-product investigation. A Solution reported as provisioned should be traceable and repairable at runtime.
Related deployment issue: existing forum post
@Vibhor.Shrivastava @diana.gray @DeaTo @zell12 @Prashanth_D @Harikishore_S1