> 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/es/installation/install-central-manager-multi-store/manage-services/central-failed-jobs.md).
# Revisar trabajos fallidos
Este tema describe cómo revisar trabajos fallidos en Central Client o Central Server.
1. Haga doble clic en el **Cliente central** o **Servidor central** icono en el escritorio.
2. Haga clic en **Trabajos fallidos**. La **Trabajos fallidos** la pestaña proporciona la siguiente información sobre los trabajos fallidos:
* Origen y destino del trabajo fallido.
* Descripción del trabajo fallido, por ejemplo, Hoja de trabajo 261 – Descargar elementos.
* El día y la hora en que falló el trabajo.
3. Haga clic en **Detalles** para ver los detalles de un trabajo fallido específico. Haga clic en **Copiar** para copiar los detalles del trabajo para que pueda pegarlos en otra aplicación, como el correo electrónico.
4. Para mostrar los trabajos fallidos de una fecha específica, seleccione la fecha en la **Fallido en fecha** campo.
5. Para actualizar la lista de trabajos fallidos, haga clic en **Actualizar**.
6. Para eliminar trabajos fallidos de la lista, seleccione el/los trabajo(s) y haga clic en **Eliminar**.
---
# 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.rmhpos.com/es/installation/install-central-manager-multi-store/manage-services/central-failed-jobs.md?ask=&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.
