Command History

Every command request is recorded: who asked, which command went to which asset, what was sent, what the equipment answered and what was read back. Everyone in your organization can read the history, whatever their role.

Command History

Open Command, then Command History. The list holds every command requested in your organization, newest first, 25 to a page.

Each row shows:

• the status, and for a critical command whether approval was required at the time: Approval required or Approval not required (tenant setting);
• the command;
• the asset and its site;
• who requested it, and its origin;
• when it was requested, and how long ago.

Select a row to open the command's record.

An asset's own Commands section lists its latest requests. See all commands on this asset opens Command History filtered to that asset; remove the asset filter with the cross beside its name.

Filters

The filters are kept in the page address, so a filtered list can be shared as a link. Clear filters removes them all.

Origin

Origin records where a request came from:

Origin is what the request declared about itself. It describes how a command was issued and grants nothing. Workflow is reserved for automated workflows, which Fleetera does not offer: no request can be recorded with it today.

The execution record

Each command has its own record page: a timeline on one side and the facts on the other.

The Timeline lists each step with its time and, where a person acted, who it was: requested, approval requested, approved or declined, sent to the gateway, completed, and the read-back. A step that has not happened yet is shown as waiting.

The Facts card holds:

For a method response, Method return values lists the returned JSON values in order, including zero, false and null. Strings appear as quoted text. The record supplies no output names, types or units.

• No outputs returned means the method returned an empty list.
• Method return values not reported means the gateway did not include the output field.
• Method return values unavailable means the gateway explicitly reported no available output value.
• Method return values invalid means the gateway's output did not have a valid JSON array shape, or contained text that cannot be stored (such as the null character). The method's success or failure is still recorded.
• Method return values could not be read: invalid result record. means the stored response could not be read safely.

The response message, Protocol status and Reported action appear when recorded. Return values describe the method's response. They do not establish measured equipment state or a verified applied value. Use separate read-back or telemetry evidence to check the equipment. An older message-only record shows Result message; a record with no result cannot supply missing return values.

If an answer arrives after cancellation or expiry, the method response says Gateway answer received after the record closed. The status remains Cancelled or Expired, and the outcome keeps its original certainty.

The record's header offers Open asset, Open run for a command in a bulk run, and Cancel before it is sent on a command that is still pending. A record awaiting approval shows the decision for an approver, see Deciding a request. A command that never reached its gateway links back to the asset's Commands section to send it again.

Bulk runs

Bulk runs, under Command History, lists every bulk run and its rollout. Each row shows the run's status, the command, its current batch and rollout policy, how many assets it targets, its progress, who requested it with its origin, and when. Select a row to open the run page.

Bulk runs has one filter, the run's status. Runs created before staged rollout say Not staged.

Exporting the ledger

Export CSV on Command History downloads every command that matches the filters on screen, not only the page you see, as command-ledger- followed by the date and .csv. While the file is prepared the button reads Preparing.

The final CSV column, result (JSON), retains the recorded response as JSON, including method return values and any answer received after the record closed. Historical message-only and null results stay as recorded; the export cannot recover missing values.

A file holds at most 50,000 rows. The notice after the download says how many commands the file holds. When more commands match than fit, the notice says the file is capped and how many matched: narrow the filters, for example by date, to export the rest.

Retention

Command History states how long the ledger is kept:

Command records are kept with no expiry date. The analytics copy keeps 365 days.