Fleet

Fleet missions

Missions are the operator console for assigning work to robots: create, schedule, start, pause, resume, cancel, complete, fail, and auto-assign. There is no separate /docs page in the Machine API tag — this is the product contract for /app/fleet/missions.

API docs

Browse docs

On this page

01 Console

details

/app/fleet/missions

List, create, auto-assign one or all, and jump into a mission. Priorities are low, normal, high, and critical.

/app/fleet/missions/:id

Start, pause, resume, cancel, complete, or fail a mission, and edit waypoint JSON.

02 Status and scheduling

details

Statuses

pending, assigned, in_progress, paused, completed, failed, cancelled. ScheduledMissionWorker starts missions whose scheduled_at has arrived and whose status is still pending.

Auto-assign

Automatic assignment picks from online robots and uses payload.required_capabilities when present. An explicit assign call only checks that the robot exists in the workspace — it can still target a retired unit. POST /api/v1/operator/missions/auto-assign-all returns {results: [...]} with the context tuples unchanged (not remapped to status/mission_id/robot_id).

Related docs