> 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.md).

# Job Manager

Use Job Manager to monitor operational health, manage service jobs, investigate file and message processing, and build data exports.

Job Manager gives operations and technical teams one place to monitor scheduled work and investigate data processing in HotWax Commerce.

Open Job Manager from the HotWax Commerce Launchpad. Your account needs the `JOB_MANAGER_APP_VIEW` permission to enter the app. See [Job Manager app permissions](/documents/system-admins/administration/introduction/job-manager-app.md) for the permissions that control each action.

## Choose a workspace

Use the app menu to open the workspace that matches your task:

| Workspace         | Use it to                                                                                               |
| ----------------- | ------------------------------------------------------------------------------------------------------- |
| `Dashboard`       | Review schedule health, queue activity, service diagnostics, file failures, and system message failures |
| `Catalog`         | Find a service job and open its configuration                                                           |
| `Run history`     | Investigate successful, failed, running, or terminated job runs                                         |
| `File history`    | Monitor files processed through master data management (MDM) configurations                             |
| `Manual uploads`  | Upload a file through an available import configuration                                                 |
| `Message history` | Trace inbound and outbound system messages                                                              |
| `Message types`   | Review or administer system message type definitions                                                    |
| `Remote systems`  | Review or administer connected-system definitions                                                       |
| `Bulk operations` | Review the bulk operations Shopify ran and the system message that requested each one                   |
| `Documents`       | Build and run data documents                                                                            |
| `Export history`  | Investigate data document exports                                                                       |
| `Settings`        | Review the active instance, product store, time zone, app version, and data status                      |

## Start an investigation

1. Open `Dashboard`.
2. Review the health cards and diagnostics.
3. Select the count or action that matches the issue.
4. Use the filtered history or detail page to inspect the affected job, file, or message.
5. Record the identifier, status, time, and error before changing a schedule or configuration.

The Dashboard is an operational summary. Use the linked history and detail pages to confirm the underlying record before taking action.

## Work in the correct context

The app menu shows the active product store and time zone. Check this context before you run a job, upload a file, or interpret a timestamp.

Changing the product store refreshes supported job, file, and Shopify bulk operation views. System messages do not use the product store as a global filter.

## Open the legacy app

Open `Settings`, then select `Go to Legacy App` when you need a workflow that is not available in the current app.

The app can also redirect to the legacy experience when the connected HotWax Commerce version does not meet the configured compatibility requirement. The compatibility threshold depends on the environment.

## Learn each workflow

* [Review the Dashboard](/documents/system-admins/administration/job-manager/dashboard.md)
* [Find a job](/documents/system-admins/administration/job-manager/jobs/catalog.md)
* [Investigate a job run](/documents/system-admins/administration/job-manager/jobs/run-history.md)
* [Monitor imported files](/documents/system-admins/administration/job-manager/manage-files-and-imports/file-history.md)
* [Trace system messages](/documents/system-admins/administration/job-manager/system-messages/message-history.md)
* [Review Shopify bulk operations](/documents/system-admins/administration/job-manager/shopify/bulk-operations.md)
* [Build a data document](/documents/system-admins/administration/job-manager/data-documents/build-data-document.md)
* [Manage app settings](/documents/system-admins/administration/job-manager/settings.md)
* [Troubleshoot Job Manager](/documents/system-admins/administration/job-manager/troubleshooting.md)


---

# 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.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.