Deployment Status
As a device works toward its desired state, it reports progress back to the platform. That feedback is what you see live in the Deployments module.
Who this is for: OT engineers connecting devices.
Reporting status
Section titled “Reporting status”A device reports status for a deployment to /deployments/:id/status (note
the plural deployments) using a manifest of kind
DeploymentStatusManifest.
The lifecycle states
Section titled “The lifecycle states”There are exactly six states, all lowercase:
| State | Meaning |
|---|---|
| pending | accepted, not yet started |
| installing | the workload is being installed |
| installed | the workload is installed and running |
| failed | installation failed |
| removing | the workload is being removed |
| removed | the workload has been removed |
A typical install runs pending → installing → installed. A failure ends in failed. Removing a workload runs removing → removed.
These are the same states surfaced on a deployment’s detail page in the web UI, aggregated across all its target devices.
No extra endpoints
Section titled “No extra endpoints”The Margo status contract is exactly the above. Fleet Manager does not add status-history, verification, or summary endpoints on top of it — see Constraints & Interoperability.