> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/tutorials/fr/automatic-actions/verifier_action_auto.md).

# Vérifier les actions automatiques

## On-premise et GLPI Network Cloud

Pour vérifier l'état de vos actions automatiques, il existe une action automatique dont le rôle est de vérifier l'état des autres.

* Allez dans le menu **`setup`** > **`Automatic actions`**, et sélectionnez l'action automatique **`watcher`**.

Cette action automatique vous enverra, par e-mail (si vous avez correctement configuré les Notifications), les actions en erreur. Plus précisément, ce sont toutes les actions dont le statut **reste indéfiniment sur "En cours"**.

Il est également possible de vérifier manuellement l'état d'une action automatique dans sa page de configuration, et de la relancer en cliquant sur la croix **`Reset`** juste à droite du statut d'exécution actuel :

![Alt text](https://1227510999-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqmRzI15ndDbFHGd5BnM4%2Fuploads%2Fgit-blob-270040dd222d502141d073ea7e431bd1e2d138ed%2Fverifier.png?alt=media)

## GLPI Network Cloud UNIQUEMENT

{% hint style="info" %}
**À savoir**

Si vous utilisez le mode d'exécution "CLI" (qui est recommandé), et que vous avez demandé l'activation, notre système interne vérifie les actions automatiques bloquées toutes les 6 heures et les débloque automatiquement.
{% endhint %}

## Références

[Documentation GLPI "Configurer les actions automatiques"](https://glpi-user-documentation.readthedocs.io/fr/latest/modules/configuration/crontasks.html)


---

# 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://help.glpi-project.org/tutorials/fr/automatic-actions/verifier_action_auto.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.