Updates a mission
Communicates updates on a mission execution. It should be called whenever a mission status changes (has started, has finished) or any of its tasks has just been completed. Times are recorded assuming these updates are called immediately.
Documentation Index
Fetch the complete documentation index at: https://inorbitinc.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
InOrbit appKey authenticates API requests using a token.
You can obtain your appKey in the Authentication docs.
Path Parameters
The mission id
Body
Mission attributes to be modified
Optional. Mission status (error, warning, ok). Most of the times this value is not needed; it will be derived from status and other fields.
Optional. Mission state. For example "running", "stuck", "late". Mostly customer-dependent; although some states will have their own semantics (configurable).
Optional. Assigns the mission to a specific robot. It can only be used when a mission has not yet been started.
Updates the task currently being executed by the robot. When updating this values, other fields are also automatically updated (such as start or end time of tasks, and overall mission progress percentage).
Optional. Whether this mission is still running. When inProgress is first changed to true, a startTs value is updated; and when changed from true to false, the endTs field is updated.
Optional. Mission description (in the PUT call, mission can be renamed).
Optional. Start time (milliseconds, epoch time). Updates the time the mission actually started. Note that there is no need to update it manually if the flag inProgress is used in POST and PUT calls.
Optional. End time (milliseconds, epoch time). Updates the time the mission ended. Note that there is no need to update it manually if the flag inProgress is used in PUT calls.
Optional. Progress of the mission; number from 0.0 to 1.0. This value can be explicitly updated; but in most cases it is not necessary: it can be calculated based on completed tasks and milestones and their declared duration.
Optional. Updates the mission estimated duration (in seconds).
Array of task objects to perform point-wise updates on mission tasks. Not all tasks in the mission are required to appear; only those to be updated. The taskId field in each task object identifies the task (it must exist in the original mission creation) and a few other fields are allowed to be updated.
Response
A Mission object containing all mission's attributes
Unique mission id
Optional. The id of the robot associated to this mission. It can only be omitted for missions that have not yet been started.
Optional. Mission status (error, warning, ok). Most of the times this value is not needed; it will be derived from status and other fields.
Is the robot currently executing the mission ?
Mission creation timestamp
List of mission tasks
Optional. Mission state. For example "running", "stuck", "late". Mostly customer-dependent; although some states will have their own semantics (configurable).
Optional. Mission description (in the PUT call, mission can be renamed).
Mission last update timestamp
Mission last update timestamp
Progress of the mission
Optional. Updates the mission estimated duration (in seconds).
Arguments passed to this mission. Free-form, key-value dictionary.
Metadata associated to this mission; including telemetry or results collected while running the mission. Free-form, key-value dictionary.
Mission last update timestamp
Id of the task currently being executed by the robot