> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/triggers/schedule.md).

# Schedule

{% hint style="info" %}
**\[Triggers -> Schedule]** We are working on this functionality. We will announce its deployment in the changelog as soon as it becomes available.
{% endhint %}

## Schedule Triggers in DLP policies

### Feature description

Triggers **Schedule** allow scheduling the execution of DLP rules at a strictly defined time, independently of other conditions. This is a useful tool for data classification within security policies.

## Schedule types

Trigger **Schedule** supports the following schedule types:

* **Hourly**– the rule is executed every 60 minutes.
* **Daily**– the rule is executed every day.
* **Weekly** – the rule is executed once a week.
* **Monthly** – the rule is executed once a month.

***

## Key configuration steps

{% stepper %}
{% step %}

#### Setting the start date

Each schedule requires defining a start date, which specifies when the rule will be first executed.
{% endstep %}

{% step %}

#### Defining the end date or number of occurrences

* If the schedule is intended to be time-limited, you should:
  * Select **an end date**,
  * Or set **the number of occurrences** of the rule.
* After the schedule reaches its end, the rule will be automatically disabled.
  {% endstep %}

{% step %}

#### Indefinite operation (optional)

* To have the rule operate without an end date, select the option **"Run Infinitely"**.
* In that case the schedule will remain active until the rule is manually disabled in the main DLP policies view.

<div align="left"><figure><img src="/files/463cf1258f9768e36ad141239a940ab882a97d36" alt="" width="188"><figcaption></figcaption></figure></div>
{% endstep %}
{% endstepper %}

***

### Additional configuration options

Depending on the selected frequency, the schedule may include additional settings.

#### Daily

* **Every X days** – execute the rule every specified number of days.
* **Every weekday** – execute the rule only on working days.

<figure><img src="/files/d8577ff1c3efac699447736f0c7b24e875114c68" alt="" width="188"><figcaption></figcaption></figure>

#### Weekly

* **Every X week(s) on the following day** – execute the rule every specified number of weeks on the indicated day.

<figure><img src="/files/9ffa8692c9f53a8d8dc47044fc46a6f8d4b8f211" alt="" width="188"><figcaption></figcaption></figure>

#### Monthly

* **Every X month(s) on X day of the month -** The rule will be executed every specified number of months (X), on a specific day of the month (e.g., the 15th day of every 3rd month).

  **Example:** If we set "every 2 months, on the 10th day of the month", the rule will run on the 10th day of January, March, May, etc.
* **Every X month(s) on a variable day: \[Week], \[Weekday]** - The rule will be executed every specified number of months (X), according to a variable day of the month.

  **Configuration options:**

  * **\[Week]:** Week number in the month (e.g., first, second, third week).
  * **\[Weekday]:** Day of the week (e.g., Monday, Tuesday).

  **Example:** If we set "every 1 month, on the second Monday of the month", the rule will be executed on the corresponding day each month.

<figure><img src="/files/2f5c314af5d92c55e3f3f8711bbd17623fbf4020" alt="" width="188"><figcaption></figcaption></figure>

***

## Summary

Trigger **Scheduled** allows precise scheduling and control of automation in DLP policies. With extensive schedule configuration options, rules can be tailored to an organization's specific needs, ensuring compliance with security policies and the effectiveness of their enforcement.


---

# 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://eaclouddoc.eauditor.eu/eacloud-docs-en/features/data-loss-prevention/dlp-policies-and-rules/triggers/schedule.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.