Skip to content
Proud to collaborate with Microsoft for Startups

agriculture.fleet.snapshot ​

Vendor-neutral mixed-fleet AEMP snapshot over connected OEMs.

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-agriculture
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
organization_uuiduuidYes—Authenticated organization UUID
cloud_connection_uuiduuidNo—Optional Deere connection UUID to filter source_ref rows
workflow_run_idstringNo—Engine-stamped parent DAG run id
pageintegerNo—One-based page; default 1

Output Schema ​

FieldTypeRequiredDefaultDescription
organization_uuiduuidYes—Authenticated organization UUID
cloud_connection_uuiduuidNo—Optional Deere connection UUID to filter source_ref rows
workflow_run_idstringNo—Engine-stamped parent DAG run id
pageintegerNo—Page echoed
assetslistYes—Normalized assets (machine_uuid when known, make, model, serial_ref, location, hours, fuel)
record_countintegerYes—Assets in this page
read_atstringYes—ISO-8601 read timestamp
coveragejsonYes—Per-vendor coverage flags (deere/cnh/caterpillar/agco) for this payload
failure_reasonstringNo—Safe terminal failure reason
failure_typestringNo—Stable failure classification
failed_actionstringNo—Action that failed
failed_stepjsonNo—Failed DAG step envelope
failed_layerintegerNo—One-based failed DAG layer
failed_at_statestringNo—State where failure occurred
errorstringNo—Safe unexpected error
error_typestringNo—Unexpected exception class
failed_atstringNo—ISO-8601 failure timestamp
provider_request_refstringNo—Safe provider request reference
retryablebooleanNo—Whether the failure is retryable

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—execute—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "agriculture.fleet.snapshot",
  "initial_data": {
    "organization_uuid": "value"
  }
}