> For the complete documentation index, see [llms.txt](https://docs.hotwax.co/documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hotwax.co/documents/system-admins/administration/job-manager/system-messages/message-history.md).

# Message history

Find inbound and outbound system messages and open their processing details.

Open `System messages` > `Message history` to trace data exchanged between HotWax Commerce and connected systems.

## Filter message history

Search for a message identifier or related value. Combine the search with:

* `Status`
* `Parent Type`
* `Type`
* `Remote`
* `Direction`

Use `Previous` and `Next` to move through result pages.

System messages do not use the product store as a global filter. Use message type, remote system, direction, and identifiers to narrow the list.

## Read a message record

A message record can show:

* System message identifier
* Message type
* Remote system
* Inbound or outbound direction
* Current status
* Created and updated times
* Parent or related message information

Select a record to open [Trace a system message](/documents/system-admins/administration/job-manager/system-messages/message-details.md).

## Start with the right identifier

Use the identifier from the failed integration, linked file, data export, or support event. Do not substitute a parent message, remote system, or adjacent message type for the exact message you need to trace.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hotwax.co/documents/system-admins/administration/job-manager/system-messages/message-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.