> ## Documentation Index
> Fetch the complete documentation index at: https://syteca.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Alert Scheduler

> Make an alert rule active only within the dates, days of the week, and time ranges you define, instead of leaving it permanently enabled.

An alert rule is either enabled or disabled for the whole system. If a rule should apply during lessons, shifts, or working hours and stop applying outside them, someone has to switch it on and off by hand.

The Alert Scheduler adds a **Schedule** section to the alert rule. You define the date range, the days of the week, and the time intervals when the rule is active. Outside those intervals the rule is inactive and does not trigger.

> [!NOTE]
>
> **Use the Alert Scheduler when you need to:**
>
> * Enforce a restriction only during class or training time, and leave the endpoint unrestricted for the rest of the day.
> * Apply a rule only on the days of the week your organization's timetable covers.
> * Limit a rule to a fixed period, such as a semester or the length of a contractor engagement.

> [!NOTE]
>
> Available from Syteca 7.28.300. The schedule applies to **Windows clients only**. macOS and Linux clients ignore the Schedule section and keep triggering alerts based on the conditions in the Rules section alone.

## Activation modes

The **Schedule** section on the **Alerts > Add/Edit Alert** page has two activation modes.

| Mode | What it does | Schedule fields |
| - | - | - |
| **Always active** | The alert is active continuously and is not restricted by dates, days of the week, or time ranges. This matches how alerts behaved before the Alert Scheduler. | Hidden |
| **Advanced schedule** | The alert is active only within the configured dates, days of the week, and time ranges. | Shown |

**Always active** is selected by default for every new alert.

![Alerts Edit alert page showing the Schedule section with the Always active activation mode selected](https://mintcdn.com/syteca/NuIWEnrWYdgsErkZ/images/session-monitoring/alerts/alert-scheduler-always-active.png?fit=max\&auto=format\&n=NuIWEnrWYdgsErkZ\&q=85\&s=37cf11205c54492e9b6b215a848e96f9)

## Configure a schedule

**1. Open the alert**

Go to the **Alerts** page and either add a new alert or open an existing one for editing.

**2. Select Advanced schedule**

In the **Schedule** section, select **Advanced schedule**. The schedule configuration fields become available.

**3. Set the active dates**

Clear the **No date restriction** checkbox to limit the schedule to a date range, then set **From** and **To**. The range is pre-filled with two weeks starting on the rule creation date, and you can change it. Leave the checkbox selected to run the schedule without any date limit, so only the days and time ranges apply.

**4. Set the time ranges**

Set **Time from** and **Time to**, then select the days of the week the range applies to. The first range is pre-filled with 08:00 to 17:00, Monday through Friday.

**5. Add further ranges**

Select **+ Add time range** to add another row with its own time and days of the week. Use this for a timetable with a break in it, such as mornings and afternoons with a lunch gap. You can add up to 10 ranges in one rule.

**6. Save the alert**

Select **Finish**. The alert now triggers only when the conditions in the **Rules** section are met and the current time falls inside the schedule.

![Alerts Edit alert page showing the Advanced schedule mode with active dates and two time ranges](https://mintcdn.com/syteca/NuIWEnrWYdgsErkZ/images/session-monitoring/alerts/alert-scheduler-advanced-schedule.png?fit=max\&auto=format\&n=NuIWEnrWYdgsErkZ\&q=85\&s=4bcc2a17e481ba34bd9e6ef2d701497c)

## Schedule settings

| Setting | What it controls | Default |
| - | - | - |
| **No date restriction** | When selected, the rule is evaluated without date-based scheduling and only the time ranges apply. The **Active dates** fields are disabled. | Selected |
| **Active dates (From / To)** | The date range during which the schedule is valid. | Pre-filled with a two-week range starting on the rule creation date |
| **Time from / Time to** | The interval during the day when the alert is active. | 08:00 to 17:00 |
| **Days of the week** | The days the time range applies to. | Monday through Friday |
| **+ Add time range** | Adds another row with its own time and days. Disabled once the rule holds 10 ranges, and enabled again after you remove one. | Maximum 10 ranges |

### Validation messages

| Condition | Message |
| - | - |
| The **To** date is earlier than the **From** date | The From value must be earlier than the To value. |
| The **Time from** value is later than the **Time to** value | The From value must be earlier than the To value. |
| No days of the week are selected | Select at least one day of the week. |

## How the schedule is evaluated

* The alert triggers only when every condition in the **Rules** section is met **and** the current time falls inside the schedule.
* The alert is active during any one matching time range. Ranges do not all have to match.
* If ranges overlap, the alert stays active for the overlapping period.
* Time ranges are same-day only. A range that crosses midnight, such as 22:00 to 06:00, is not supported.
* If all rule conditions are met outside the scheduled time, the alert does not trigger on the client and does not appear in the system.
* The schedule still applies while the client is offline. Alerts trigger according to the rules and the schedule, and reach the Application Server when the client reconnects.
* Alerts triggered on a schedule behave exactly like standard alerts once they triggered, including notifications and additional actions.

> [!WARNING]
>
> When the **Active dates** range expires, the rule continues to be evaluated **without** scheduling, and alerts trigger regardless of the dates, times, and days of the week configured. The rule setup is not changed, so the schedule stays visible on the page while no longer limiting anything. Review rules with an end date before the date passes.

## Example

A school blocks access to personal email on classroom endpoints during lessons, but allows it between lessons.

| Setting | Value |
| - | - |
| Active dates | 01.09 to 31.12 (the semester) |
| Time range 1 | 08:00 to 12:00, Monday through Friday |
| Time range 2 | 13:00 to 15:00, Monday through Friday |

Results:

* Between 07:00 and 08:00, and between 12:00 and 13:00, students can open email and the alert does not trigger.
* Between 08:00 and 12:00, and between 13:00 and 15:00, the alert is active. When a user opens email, the alert triggers, shows the warning message, and closes the application according to the configured action.

## After an upgrade

All alert rules that existed before the upgrade stay in **Always active** mode. No schedule is applied to them, and their behavior does not change.

## Multi-tenant and high availability

> [!NOTE]
>
> In multi-tenant mode, the **Schedule** section is available to every tenant, and the scheduling logic works the same for a non-default tenant as for the default tenant. In load-balanced deployments, schedule changes are shared across all nodes.

## Audit log entries

Adding or editing an alert records the schedule in the [audit log](/docs/administration/audit-log) under the **Alert management** category.

## Related

> **[Alerts](/docs/session-monitoring/alerts)**
>
> Add, edit, assign, and manage alerts.

> **[Alert rules](/docs/session-monitoring/alert-rules)**
>
> Build the conditions that the schedule applies to.

> **[Alerts and events](/docs/session-monitoring/alerts-events)**
>
> Review the alert events that were triggered.

> **[Audit log](/docs/administration/audit-log)**
>
> See who changed an alert schedule and when.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.