> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.7.0/helmut4-components/helmuthk/cron.md).

# Cron

Via the cron menu, cron jobs can be created for tasks as well as for active directories. This makes it possible to automatically execute tasks at regular intervals, or to automatically synchronise AD groups with Helmut groups.

<figure><img src="/files/So9Qc2rx9CKumuWAewRi" alt=""><figcaption><p>Cron Job Menu</p></figcaption></figure>

### Status:

Shows the status of the selected cron job. If the status is OK, the defined parameters within the cron job are valid.

### Type:

Shows the type of the created cron job. This can be e.g. Task or Active Directory

### Next Execution:

Displays the date of the next execution.

### Action Button:

A cron job can be modified via the action button. It is possible to edit, duplicate, execute or delete an entry. When an entry is edited, the same dialog opens as the Add Cronjob button.


---

# 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.helmut.de/helmut4-releases/v4.7.0/helmut4-components/helmuthk/cron.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.