> 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/retail-operations/workflow/workflow/troubleshooting.md).

# Troubleshooting

Choose the current Job Manager workflow for a job, file, message, or export issue.

Start with the identifier and current status of the affected record. Use the page that owns that record:

| Problem                                                 | Start here                                                                                                                      |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| A job did not run, failed, or has the wrong schedule    | [Troubleshoot job runs and schedules](/documents/retail-operations/workflow/workflow/troubleshooting/job-runs-and-schedules.md) |
| A file is pending, failed, or contains rejected records | [Troubleshoot file imports](/documents/retail-operations/workflow/workflow/troubleshooting/file-imports.md)                     |
| An integration message failed or stopped                | [Troubleshoot system messages](/documents/retail-operations/workflow/workflow/troubleshooting/system-messages.md)               |
| A data document export failed or did not arrive         | [Troubleshoot data document exports](/documents/retail-operations/workflow/workflow/troubleshooting/data-document-exports.md)   |

## Capture evidence first

Record:

* Exact job, run, file, message, or export identifier
* Current status
* Instance, product store when applicable, and time zone
* Start and completion times
* First actionable error
* Parameters or configuration used

Do not rerun, resubmit, or change status until you confirm whether the original request is still processing.

## Refresh stale app data

Open `Settings` > `Data Fetch Status`. Refresh the affected data source, then return to the record.

Use `Refresh All` only when multiple reference-data areas are stale.


---

# 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 dynamically 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/retail-operations/workflow/workflow/troubleshooting.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 `build a script that syncs our docs to a CMS` 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.