> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/installation/install-central-manager-multi-store/manage-services/central-failed-jobs.md).

# Review failed jobs

1. Double-click the **Central Client** or **Central Server** icon on the desktop.
2. Click **Failed Jobs**. The **Failed Jobs** tab provides the following information about failed jobs:

* Origin and destination of the failed job.
* Description of the failed job, e.g., Worksheet 261 – Download Items.
* The day and time the job failed.

<div align="left"><img src="/files/YLYP0br6rZ1LdsFwqrCY" alt=""></div>

3. Click **Details** to see the details of a specific failed job. Click **Copy** to copy the job details so you can paste it into another application, such as email.

<div align="left"><img src="/files/wWc3RqLWfjHHXRlxNz9p" alt=""></div>

4. To display failed jobs for a specific date, select the date from the **Failed on Date** field.
5. To refresh the list of failed jobs, click **Refresh**.
6. To delete failed jobs from the list, select the job(s) and click **Delete**.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rmhpos.com/installation/install-central-manager-multi-store/manage-services/central-failed-jobs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
