> 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/jobs/job-details.md).

# Job details

Review a service job, run it, manage its schedule and parameters, and inspect recent executions.

Open `Jobs` > `Catalog`, then select a job. The page shows the job state, description, category, and three tabs: `Overview`, `Parameters`, and `History`.

## Review the job before changing it

Use `Overview` to confirm:

* Service name, topic, and job type
* Priority, transaction timeout, retry timing, and lock limit
* Product and parent-job metadata
* Permission group
* Created and updated timestamps
* Cron expression, repeat count, and validity dates

Check the displayed permission group before you run or edit the job. A job-specific backend permission can apply in addition to app access.

## Run a job now

`Run Now` starts an immediate execution with the current job configuration.

1. Review `Parameters`.
2. Select `Run Now`.
3. Review the confirmation.
4. Confirm `Run Now`.
5. Open `History` or `Run history` to monitor the new run.

Do not run a job only to test whether it works. Confirm the job purpose, active product store, and parameters first.

## Pause or resume a schedule

1. Open `Overview`.
2. Find the `Schedule` card.
3. Select `Pause` or `Resume`.
4. Confirm the action when prompted.

Pausing a schedule prevents future scheduled runs. It does not cancel a run that already started.

## Edit a schedule

1. Open `Overview`.
2. Select `Edit` in the `Schedule` card.
3. Update `Cron Expression` and the other available schedule fields.
4. Review the human-readable cron description.
5. Save the schedule.

Confirm the instance time zone before you change a cron expression. Open `Settings` to review or change the time zone used by the app.

## Edit custom parameters

The `Parameters` tab shows supported service inputs, including optional inputs with no saved value. A blank optional value is not automatically a configuration error.

1. Open `Parameters`.
2. Select `Edit` or `Add`.
3. Enter all required parameter values.
4. Review optional values.
5. Select `Save`, or select `Cancel` to discard the edits and retain the saved values.

![Parameters tab showing a configured facilityId and a blank optional pageSize](https://213371163-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvRjh4vkGRczeQJMpDxzL%2Fuploads%2Fgit-blob-164e8e9fa362a9e67a89d7f436a2c0e9c853a5b4%2Fjob-parameters.jpg?alt=media)

*Optional parameters remain visible even when no value is set.*

For a Map, List, or Object parameter, review the JSON displayed in the field and retain its object or list structure. For example, a map looks like `{"key":"value"}`; do not add another pair of quotes around the entire JSON value.

The `Save` action remains unavailable while a required value is missing. Parameter changes affect later runs, including a run started with `Run Now`.

## Review job history

Open `History` to inspect runs for this job. The tab loads 20 runs initially; scroll to the bottom to load older runs when more are available. Use the search, `Status`, `User`, and `Data logs` filters to narrow the loaded history.

When you open `View run` from the Dashboard, the `Run #...` chip limits the history to that execution. Clear the chip to return to the job's broader history.

![Job History filtered to one run with a removable run chip](https://213371163-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvRjh4vkGRczeQJMpDxzL%2Fuploads%2Fgit-blob-a0bec49d66af8932344774718fa046032b12fcee%2Fjob-history-pinned-run.jpg?alt=media)

*Confirm the run identifier before reviewing its recorded parameters, results, and errors.*

Expand the available sections to review:

* Message
* Linked data logs
* Technical Details: Parameters, Results, and Errors when available

Open a linked data log to move to its file detail.

Use [Run history](https://docs.hotwax.co/documents/system-admins/administration/job-manager/jobs/run-history.md) when you need filters or a broader view across jobs.


---

# 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/jobs/job-details.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.
