Assign tasks to AMR (Autonomous Mobile Robot) fleets via a fleet management API and handle dynamic re-tasking on exception

Steps

1. Authenticate with the AMR fleet management system (e.g. 6 River Systems Chuck, Locus Robotics, or equivalent) using the provided OAuth 2.0 client credentials; obtain a bearer token scoped to task management
2. Submit a pick task via POST to the fleet management task endpoint: include the task type (pick, transport, putaway), origin location, destination location, order reference, and priority level; receive a task ID
3. Poll the task status endpoint or subscribe to task event webhooks to track transitions: QUEUED, ASSIGNED (robot selected), IN_PROGRESS, COMPLETED, or FAULTED
4. On a FAULTED event, read the fault reason code from the event payload; for navigation faults (path blocked), call the re-task endpoint to reassign the task to the next available robot; for item-not-found faults, escalate to a human picker
5. Monitor robot battery levels via the fleet status endpoint; when a robot reports battery below the configurable low threshold (commonly 20%), issue a charge-return task with higher priority than pending pick tasks
6. Track completed task timestamps and location confirmation data; reconcile against WMS pick confirmations to detect discrepancies where a robot reported completion but the WMS pick task shows no confirmation