Get a specific DeviceOperations for a specific Operation (Device Operation Status)
Retrieves the status of a single device's progress within a specific Dispatch operation.
Use this endpoint to check exactly where one device stands inside a larger fleet operation, including its full state history from creation through to success or failure. This is the most granular status check available for Dispatch operations such as Converge, install, and uninstall.
About Device Operation Status
Every device targeted by an Operation gets its own DeviceOperation record, which moves independently through Created, Initiated, Dispatched, Processing, and a terminal state such as Success, Failure, Cancelled, or Timeout. The device_operation_activity array on the response captures a timestamped history of every state transition for that device, useful for diagnosing exactly when and where a device stalled or failed.
Common Use Cases
Diagnosing why one specific device failed a Converge operation while the rest of the fleet succeeded
Confirming a device has reached Success before considering a bulk install or uninstall complete for that device
Reviewing the timing between dispatch and completion for a single device
Best Practices
Check device_operation_activity for the full timeline rather than relying on the current state alone
If a device is stuck in Dispatched or Processing, confirm its connectivity with GET /device/v0/heartbeat/{id}/ before assuming the operation failed
Pair this with GET /v0/operations/{operationsId}/devices/ when you need to move from a fleet-wide failure list down to individual device detail
Workflow
Identify the operationsId and deviceId, typically from the device operation list endpoint
Call this endpoint to retrieve the device's current state and activity history
If the device shows a failure or timeout state, check its last-seen connectivity before retrying
Include the device_id again in a new Operation if it needs to be re-dispatched
Path parameters
ID of the Operation
ID of the Device
Response
Device Operation information for the Operation
Example response
{
"content": {
"device_operation_activity": [
{
"device_operation_state": "CREATED"
}
]
}
}