# Command History

Multiple events are recorded in the Command History tile. Each line item will have a Result, Details, and Delete action.

![Command History Tile](/files/A0H8UjAyqPDECXiucFv4)

When an rTTY session is executed, this is a displayed command history. Selecting the Result icons will display the Success or Fail of the command.

![rTTY Command History](/files/BLRNz2tHuc3iG2vqI6zm)

Each provisioning event is reflected as a configure command history. To see the entire JSON payload and the result, including success or error with message, simply select Details to expand the dialog below with this data. A date and time in the third column indicates when the configure command was executed successfully.

![Configure Command History](/files/w73pWid3OpdED38fjvoV)

If a provisioning event has failed to complete, its command history for configure will show as pending.

![configure Pending Command History](/files/B7wfLulQPaZ5AczlRY2W)

Remote packet capture is shown as the trace command history. When packet captures are persisted in the OpenWiFi SDK, they may be downloaded again through the cloud download icon.

![trace Command History](/files/vVEwZyDVRRsxzjcxZySN)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://tip-1.gitbook.io/openwifi/sdk/user-interface/devices-view/command-history.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.