All pages
Powered by GitBook
1 of 3

Automatic actions

Setting up automatic actions

In most cases, this problem comes from the execution mode of the automatic action.

In GLPI mode, it is normal for your actions to have trigger problems at night / weekend, because these actions are only triggered by user activity in GLPI interface.

In CLI mode, however, automatic actions will be triggered by our internal system, regardless of activity in GLPI.

CLI mode is therefore recommended, it is activated by default on paid instances (triggering every 15 minutes), if you are in a test period, do not hesitate to contact us, we can activate it on demand.

References

Documentation GLPI "Configure automatic actions"

Check automatic actions

On-premise and GLPI Network Cloud

To check the status of your automatic actions, there is an automatic action whose role is to check the status of the others.

  • Go to the menu setup > Automatic actions, and select the watcher automatic action.

This automatic action will send you, by e-mail (if you have correctly configured Notifications), the actions in error. More precisely, these are all actions whose status remains indefinitely on "In progress".

It is also possible to manually check the status of an automatic action in its configuration page, and to restart it by clicking on the Reset cross just to the right of the current execution status:

Alt text

GLPI Network Cloud ONLY

To know

If you use the "CLI" execution mode (which is recommended), and you have requested activation, our internal system checks for blocked automatic actions every 6 hours and unblocks them automatically.

References

Documentation GLPI "Configure automatic actions"