> For the complete documentation index, see [llms.txt](https://docs.dataspace.ch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataspace.ch/platform/schedules.md).

# Schedules

In cases where the pipeline should be run periodically, for example, to extract data daily, Schedules can be created.

### Create a Schedule

* Select the desired transformations to be run.
* Choose a name for the Schedule.
* Click the **Create** button in the Schedule panel.

{% hint style="info" %}
Please note that only users with the [EDITOR](/platform/user-roles.md#editor) role or higher are authorized to create new schedules.
{% endhint %}

<figure><picture><source srcset="/files/1EJXTSH4kehAVzi3nSRj" media="(prefers-color-scheme: dark)"><img src="/files/miRGbktwFHlJ58XJMvL1" alt="Schedule View"></picture><figcaption></figcaption></figure>

After a schedule is created, certain properties can be modified.

### Schedule Name

The Schedule can be renamed by double-clicking on the Schedule name.

### Pause/Resume

The button next to the Schedule name allows the schedule to be deactivated without deleting the entire Schedule.

### Cron

The Cron value specifies the frequency of the run and is based on the standard cron notation. For more information, see the [wiki article](https://de.wikipedia.org/wiki/Cron).

### Next Run

Next Run displays the next time this schedule will run.

### Transforms

The transforms panel inside the Schedule widget shows all target transforms that are associated with the current Schedule. Here, transforms can be added or removed.

{% hint style="info" %}
Before a schedule executes, the list of target transforms is evaluated as a DAG and executed sequentially according to the dependency graph.
{% endhint %}

## Failing Schedules

To prevent unnecessary resource waste, the Schedules will be disabled after 3 consecutive build failures, and the creator of the schedule will be notified via email.

{% hint style="info" %}
This behavior can be adjusted with the `MAX_SCHEDULE_FAIL_COUNT` property in the `.env` file.
{% endhint %}