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

# Dashboard

Review schedule, queue, file, message, and service health from the Job Manager Dashboard.

Open `Dashboard` to review operational health and investigate the records behind a warning. Check the displayed time window before interpreting a count; recent activity does not represent all historical failures.

## Review schedule health

Use the schedule summary to compare active, paused, unscheduled, and draft jobs. Select a status to open `Catalog` with that filter, then review the job before changing its schedule or running it.

## Investigate a failed file import

1. Locate the `High-priority ingestion` or `Standard ingestion` card.
2. Select `View n Failed`.
3. In `File history`, review the priority, failure, and time filters carried over from the Dashboard.
4. Open the affected file and inspect its error information.

![Dashboard with View Failed actions for high-priority and standard ingestion](https://213371163-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvRjh4vkGRczeQJMpDxzL%2Fuploads%2Fgit-blob-d44693ee62dfa651204d9d9e70635b267e33e21e%2Fdashboard-drilldowns.jpg?alt=media)

*The ingestion actions open File history with the matching priority and time window.*

Incoming and outgoing message error totals summarize message activity. Open [Message history](https://docs.hotwax.co/documents/system-admins/administration/job-manager/system-messages/message-history.md) to investigate the underlying messages.

## Read the Queue Operations Map

Use the `Queue operations map` to review pending files and queued messages. Select the relevant stage to open its filtered history, then inspect the record's status and timestamps.

## Investigate a failed job run

1. Under `Service Jobs Diagnostics`, locate the failed job.
2. Select `View run` to open the job's `History` tab.
3. Confirm that the `Run #...` chip identifies the run you selected.
4. Review the run's status, user, start and completion times, and technical details.
5. Clear the run chip when you want to review other executions.

![Queue operations map and a failed job with a View run action](https://213371163-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvRjh4vkGRczeQJMpDxzL%2Fuploads%2Fgit-blob-d58debb76be40d0297feb97f9f9171d04b665a39%2Fdashboard-diagnostics.jpg?alt=media)

*View run opens the selected execution in the job's History tab.*

`View run` opens the execution details. `Run Now` starts another execution. Review the failure before deciding whether to rerun the job.

For configuration diagnostics, open the job and compare its `Overview`, `Parameters`, and `History`. See [Manage a job](https://docs.hotwax.co/documents/system-admins/administration/job-manager/jobs/job-details.md).

## Review recent activity

Use `Recent Activity` to open the related job, file, or message. Confirm its identifier and status on the detail page.

## Refresh dashboard data

Open `Settings` when a section appears stale. Review `Data Fetch Status`, then refresh the affected data source or use `Refresh All`.

See [Manage Job Manager settings](https://docs.hotwax.co/documents/system-admins/administration/job-manager/settings.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/dashboard.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.
