Skip to content

Mission Feedback

Mission feedback reports the progress and outcome of a running mission back to the cloud.

  • Direction: Uplink (robot → cloud)
  • Topic: the robot/mission key on the local Zenoh session (a sub-key of robot/**)
  • 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, aborted, failed).
Progress How far along the run is.
Result / outcome Final result when the run ends.

Fields

Correlate feedback with the originating mission via its run id:

Field Notes
missionRunId Identifier of the run. Matches the missionRunId on the mission command.
status Run status / lifecycle state (MissionStatus).
progressX100 Progress as percent × 100 (0..=10000).
currentStepIndex Current waypoint or checkpoint index.
currentTarget / finalTarget Optional WGS84 poses: where the robot is navigating now, and the mission's final destination.
distanceRemainingM Remaining distance, meters.
elapsedTimeMs Milliseconds since execution began.
estimatedTimeRemainingMs Remaining time, milliseconds. This estimate can move.
unixTimeMs Epoch-ms time of the update.

For the complete MissionRunStatus schema, covering every field, the progressX100 encoding, and the MissionStatus enumeration, see Uplink Messages → missionRunStatus.

Tip. Always echo the missionRunId from the mission command so the cloud can correlate feedback with the correct run. A scheduled mission is fired with the same id the server assigned when it was created.

Report a terminal status (completed, aborted, rejected, or failed) when the run ends. The robot software owns the final state: nothing else closes the run out for you. Timing on this message is elapsed and remaining duration. There is no completion timestamp.

Publishing