← All ideas
0

Robots: Queue runs instead of failing as busy when another workspace run is active

LaunchedRobotsFix

UiPath Orchestrator queues pending jobs per robot and only raises an alert when a trigger cannot create jobs (https://docs.uipath.com/orchestrator/standalone/2023.4/user-guide/alerts), and Browse AI queues tasks for bulk runs (https://www.browse.ai/monitoring). Our startRobotRun inserts a run only when no other run in the workspace is running, otherwise returns busy (lib/robots.ts). For schedules, runDueRobots advances next_run_at before starting, so a collision with a manual or Flow run records a failed busy run and that scheduled execution is lost; from Flow, app.robot_run fails unless the node has retries (default 0, lib/flow-engine.ts robotNode). Teams with two or three robots will see random failures they did not cause, which destroys trust. First scope: add a queued status, insert as queued when busy, and drain the queue in /api/cron/robots and after each run finishes, with a max queue age. Priority: high. Effort: M. Compared with UiPath (StudioX, Autopilot, Orchestrator, Healing Agent), Browse AI, Axiom.ai, Bardeen, Browserbase/Stagehand, Skyvern.

Comments 0

No comments yet.