Mission Feedback
Mission feedback reports the progress and outcome of a running mission back to the cloud.
- Direction: Uplink (robot → cloud)
- Topic:
uplink/robot/{robot_id}/{message_type} - Encoding: Cap'n Proto over Zenoh
After your robot accepts a mission command, publish feedback so the cloud can track run status and progress.
What to report
| Concept | Purpose |
|---|---|
| Run status | The lifecycle state of a mission run (e.g. accepted, running, paused, completed, failed). |
| Progress | How far along the run is. |
| Result / outcome | Final result when the run ends. |
Fields
Correlate feedback with the originating mission via identifiers:
| Field | Notes |
|---|---|
mission_id |
Identifier of the mission. |
run_id |
Identifier of the specific run (matches the run_id assigned when the mission fired). |
status |
Run status / lifecycle state. |
progress |
Progress indicator. |
timestamp_ms |
Epoch-ms time of the update. |
Detailed field schemas (status enumerations, progress representation, and result types) are coming soon.
!!! tip
Always echo the run_id from the mission command so the cloud can correlate feedback
with the correct run. Scheduled missions are fired with a fresh run_id.
Publishing
- Native: publish to
uplink/robot/{robot_id}/{message_type}. See Custom Integrations. - ROS 2: map your status topics through the bridge. See Telemetry Mappings.