Hi forum team, can you please route this to the appropriate team for resolution? This is a developer experience issue.
Description:
When a solution containing a BPMN (Maestro) that uses “Start and wait for API workflow” (or Run Job to RPA/API) is deployed for debugging, the API workflow is not published to the personal workspace debug folder — even with the tenant setting “Automatically configure Serverless machines in Personal Workspace for Studio Web users” enabled. Only the BPMN and some agents deploy; the referenced API workflow is silently dropped. This leads to a runtime “Process not found” error instead of an upfront validation warning.
Reproduction:
- Create solution with BPMN referencing an API workflow.
- Deploy Solution for Debugging in Studio Web.
- Run the BPMN → API workflow missing in debug folder.
In Test Cloud staging (UiPath) →
when developing the “Agentic Release Assurance Control Tower” hackathon 2026 project (Agentic Release Assurance Control Tower | Devpost →
a Maestro BPMN orchestrating AI agents and a Test Manager API workflow (“Execute Selected Test Set API”) fails to deploy the API workflow to the personal workspace debug folder. Only the BPMN and some agents appear; the referenced API workflow is silently dropped, resulting in a runtime “Process not found” error.
Reproduction: Deploy Solution for Debugging in Studio Web → Run BPMN → API workflow missing.
Expected:
All referenced project types (API workflow, RPA, agents) should deploy to the debug folder, or the designer should validate and warn early about runtime requirements.
Impact: Blocks end-to-end solution debugging for mixed BPMN + API/RPA flows.
Products involved: Studio Web, Solutions, API Workflow, Orchestrator (Personal Workspace), Debug
Screenshots:
CC: @Vibhor.Shrivastava @diana.gray @DeaTo @zell12 @Prashanth_D @Harikishore_S1