> 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/consistency-checker/consistency-checker-central-client-flash.md).
# Ejecutar manualmente en Central Client
Este tema describe cómo ejecutar manualmente el Comprobador de coherencia en Central Client.
{% hint style="info" %}
Los servicios del Servidor Central deben estar en ejecución para usar el Comprobador de Consistencia.
{% endhint %}
En el equipo donde **Cliente central** está instalado:
1. Abrir **Cliente central**. El acceso directo debería estar disponible en su escritorio.
2. Haga clic en **Panel de control**.
3. Haga clic en **Detener servicios**.
4. En la pantalla **Comprobador de consistencia** pestaña, seleccione la(s) fecha(s) para las que desea ejecutar la comprobación de consistencia.
5. Seleccione los tipos de transacciones que desea comprobar:
* Ventas
* Entrega/Pago
* Pedidos
* Órdenes de compra/Transferencia
* Reloj de fichar o tarjeta de horas
6. Haga clic en **Ejecutar**.
Después de que se complete la comprobación de consistencia, los servicios del cliente se reinician automáticamente. El registro de cada comprobación se guarda en **C:\ProgramData\RetailHero\Consistency Checker\Logs**.
---
# 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/consistency-checker/consistency-checker-central-client-flash.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.
