> 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/triggers/schedule.md).

# Schedule

(In preparation)

Trigger **Schedule** enables automatic launching of the DLP rule according to a specified time cycle.

You can use it when the rule should be executed:

* every day or every specified number of days,
* only on weekdays,
* on a selected day of the week,
* on a specified day of the month,
* recursively for a specified period,
* indefinitely.

The Trigger operates independently of events performed directly by the user, such as connecting a device or sending a file.

{% hint style="info" %}
The Schedule is primarily suitable for rules that should be run recursively, for example during periodic classification or file tagging.
{% endhint %}

### Schedule types

There are three basic ways to run a rule recursively:

| Type        | Action                                                                               |
| ----------- | ------------------------------------------------------------------------------------ |
| **Daily**   | Runs the rule every day, every specified number of days, or only on weekdays         |
| **Weekly**  | Runs the rule recursively on a specified day of the week                             |
| **Monthly** | Runs the rule on a specified day of the month or based on a selected day of the week |

<mark style="background-color:$primary;">\[Insert screen 1 - Medium size]</mark>

<mark style="background-color:$primary;">**Alt:**</mark> <mark style="background-color:$primary;"></mark><mark style="background-color:$primary;">Configuration of the Schedule trigger in a DLP rule with the option to select a daily, weekly, or monthly schedule.</mark>

*<mark style="background-color:$primary;">The schedule type determines the frequency of automatic rule execution.</mark>*

### Schedule configuration

{% stepper %}
{% step %}

#### Add trigger

When creating or editing a rule, go to the section:

**Triggers**

Click **Add step**, then select the trigger **Schedule**.
{% endstep %}

{% step %}

#### Select the schedule type

Specify how the rule should run recursively:

* daily,
* weekly,
* monthly.

After you select a type, the settings appropriate for that schedule will be displayed.
{% endstep %}

{% step %}

#### Set the start date

Specify the schedule start date.

This date determines when the rule can start running according to the configured cycle.
{% endstep %}

{% step %}

#### Specify the end method

If the schedule is to run for a limited time, specify:

* the end date,

or

* the number of rule occurrences.

After the schedule ends, the rule will no longer be triggered by this trigger.
{% endstep %}

{% step %}

#### Set indefinite execution

If the schedule should not have a defined end, enable the option:

**Run Infinitely**

The rule will then run according to the schedule until the configuration is changed manually or the rule is disabled.
{% endstep %}

{% step %}

#### Save the configuration

After setting the schedule, save the rule.

After completing the configuration, remember to use the option:

**Update policies**

so the latest configuration can be distributed to eAgents.
{% endstep %}
{% endstepper %}

<mark style="background-color:$primary;">\[Insert screen 2 - Medium size]</mark>

<mark style="background-color:$primary;">**Alt:**</mark> <mark style="background-color:$primary;"></mark><mark style="background-color:$primary;">Start date, end date, and indefinite execution settings for the Schedule trigger.</mark>

*<mark style="background-color:$primary;">The schedule can run for a specified time, a specified number of occurrences, or indefinitely.</mark>*

### Daily schedule

In daily mode, you can define how often the rule should be run.

Available options include:

* **Every X days** - run the rule every specified number of days,
* **Every weekday** - run the rule only on weekdays.

#### Example

If you set:

**Every 2 days**

the rule will run every two days from the specified start date.

If you select:

**Every weekday**

the rule will run on weekdays.

<mark style="background-color:$primary;">\[Insert screen 3 - Medium size]</mark>

<mark style="background-color:$primary;">**Alt:**</mark> <mark style="background-color:$primary;"></mark><mark style="background-color:$primary;">Daily DLP schedule configuration with Every X days and Every weekday options.</mark>

*<mark style="background-color:$primary;">The daily schedule can run every specified number of days or only on weekdays.</mark>*

### Weekly schedule

Weekly mode lets you define:

* how many weeks should pass before the rule is run,
* on which day of the week execution should occur.

#### Example

The configuration can define rule execution:

**every 2 weeks on Monday**

This way, the rule does not have to be executed every week.

<mark style="background-color:$primary;">\[Insert screen 4 - Medium size]</mark>

<mark style="background-color:$primary;">**Alt:**</mark> <mark style="background-color:$primary;"></mark><mark style="background-color:$primary;">Weekly DLP schedule configuration with frequency and day-of-week selection.</mark>

*<mark style="background-color:$primary;">The weekly schedule lets you specify the cycle and the day on which the rule is executed.</mark>*

### Monthly schedule

Monthly mode enables you to define rule execution in two ways.

#### Specified day of the month

You can specify:

* how many months the rule should run,
* a specific day of the month.

Example:

**every 2 months, on the 10th day of the month**

The rule will be executed on the 10th day in subsequent months according to the configured cycle.

#### Specified day of the week in the month

It is also possible to specify:

* monthly frequency,
* week number,
* day of the week.

Example:

**every month, on the second Monday of the month**

The rule will be run on the second Monday of every month.

<mark style="background-color:$primary;">\[Insert screen 5 - Medium size]</mark>

<mark style="background-color:$primary;">**Alt:**</mark> <mark style="background-color:$primary;"></mark><mark style="background-color:$primary;">Monthly DLP schedule configuration with the option to select a day of the month or a specified day of the week.</mark>

*<mark style="background-color:$primary;">The monthly schedule can use a specific day of the month or, for example, the second Monday of the month.</mark>*

### When should you use a schedule?

Use a schedule when the rule should not be initiated by a single user action, but should run recursively.

An example is periodic document tagging.

An administrator can configure a rule that:

1. runs according to the schedule,
2. checks the specified files,
3. identifies files that meet the specified criteria,
4. assigns them the appropriate tag.

As a result, classification can be performed recursively without the need to manually start the operation.

{% hint style="info" %}
File tagging can run recursively according to a schedule. The system can then scan the specified areas and tag files that meet the configured criteria.
{% endhint %}

### Schedule and other triggers

The Schedule differs from most other triggers.

Triggers such as:

* **Copying**,
* **USB device connection**,
* **File sending**,
* **Process/application launched**

respond to a specific event occurring on the computer.

**Schedule** starts an action based on the configured time cycle.

{% hint style="info" %}
If the rule should respond directly to a user action, select the trigger corresponding to that action. Use Schedule when the action should be initiated recursively.
{% endhint %}

### Schedule testing

After creating a schedule, it is worth checking its behavior before deploying the rule to a larger number of computers.

{% stepper %}
{% step %}

#### Set the test scope

Assign the policy to the selected test computer.
{% endstep %}

{% step %}

#### Set a close date

For testing purposes, configure the schedule so that its execution can be verified without a long wait.
{% endstep %}

{% step %}

#### Update policies

Click **Update policies** and make sure the computer is communicating with eAuditor Cloud.
{% endstep %}

{% step %}

#### Wait for execution

After the schedule deadline occurs, verify that the configured action was performed.
{% endstep %}

{% step %}

#### Check DLP Logs

If the rule action is logged, go to:

**Data Leak Prevention -> DLP Logs**

and review the information about its execution.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
After completing the test, remember to restore the correct schedule before applying the policy in the production environment.
{% endhint %}

### FAQ

<details>

<summary><strong>Can the schedule run without an end date?</strong></summary>

Yes. Enable the option **Run Infinitely**.

The schedule will run indefinitely until the configuration is changed or the rule is disabled.

</details>

<details>

<summary><strong>Can I run the rule only on weekdays?</strong></summary>

Yes. The daily schedule includes the option **Every weekday**.

</details>

<details>

<summary><strong>Can the rule run every few days?</strong></summary>

Yes. The option **Every X days** lets you specify the number of days between executions.

</details>

<details>

<summary><strong>Can I run the rule, for example, on the second Monday of every month?</strong></summary>

Yes. The monthly schedule lets you specify the appropriate week number and day of the week.

</details>

<details>

<summary><strong>Can I limit the number of rule executions?</strong></summary>

Yes. Instead of indefinite execution, you can specify an end date or the number of rule occurrences.

</details>

<details>

<summary><strong>Does Schedule respond to user actions?</strong></summary>

Not directly. The trigger starts the rule based on the configured time cycle.

If you want to respond to a specific user action, such as copying a file or connecting a USB drive, use the appropriate event trigger.

</details>


---

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