> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/calendar-trigger.md).

# Calendar Trigger

Run a rule chain at a daily, weekly, or monthly calendar time.

Use the **Calendar** trigger to run a rule chain at a specific time each day, on selected weekdays, or on a selected day of the month. For example, run a monthly report at 08:00 on the last day of every month.

Before you begin, [open the rule chain editor](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/open-the-configuration-of-an-existing-rule-chain.md). Keep the chain paused until its nodes and recipients are configured.

## Configure the calendar

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-2656f109f7fb70ae679d2ad8e7fab6facbef4a25%2Frule-chain-calendar.png?alt=media" alt="Calendar Configuration showing Monthly recurrence, an exact date of 31, the skipped-date notice, and execution time 08:00."><figcaption><p>Calendar configuration with an exact monthly date</p></figcaption></figure></div>

| Callout  | Setting      | Description                                                                                   |
| -------- | ------------ | --------------------------------------------------------------------------------------------- |
| **\[A]** | Recurrence   | Select Daily, Weekly, or Monthly.                                                             |
| **\[B]** | Execute date | For Monthly, select Exact date, Every first day of the month, or Every last day of the month. |
| **\[C]** | Day of month | For Exact date, select a day from 1 to 31.                                                    |
| **\[D]** | Execute time | Enter the time in `HH:mm` format.                                                             |
| **\[E]** | Save         | Apply the calendar settings to the editor. Save the chain separately to retain them.          |
| **\[F]** | Date notice  | Dates that do not occur in a month are skipped.                                               |

1. Select **Calendar** in the editor's **Trigger** list.
2. Click the gear icon beside the calendar summary.\
   ▷ The **Calendar Configuration** dialog opens.
3. Select **Recurrence** **\[A]**.
4. Configure the days for the selected recurrence:
   * **Daily**: Continue to the execution time.
   * **Weekly**: Select at least one weekday.
   * **Monthly**: Choose an **Execute date** option **\[B]**. For **Exact date**, select the day **\[C]**.
5. Enter **Execute time** **\[D]**, for example `08:00`.
6. Click **Save** **\[E]**.\
   ▷ The calendar summary in the editor shows the schedule and its time zone.
7. Check the time zone in the summary.\
   ◈ The initial time zone comes from your browser and is saved with the schedule.
8. Click **Save** in the editor.
9. Enable the chain when its configuration is ready.\
   ▷ The chain waits for the next scheduled execution.

## Monthly dates

An exact date does not move to a different day in a shorter month. For example, day **31** does not run in April, and day **29** does not run in February in a non-leap year.

Select **Every last day of the month** to run every month on its actual final day, including February. Select **Every first day of the month** for a monthly run on day 1.

## Execution behavior

* An enabled chain runs according to its saved calendar and time zone.
* Times missed while the chain is paused or the service is unavailable are not replayed.
* Executions do not overlap. If an execution is still running at a later scheduled time, that time is skipped.
* Daylight-saving changes can make local times nonexistent or ambiguous. Prefer a time outside the transition hours, such as `08:00`.

{% hint style="info" %}
For an action that must run at every calendar execution, set its **Trigger mode** to **Always** and provide a true Trigger input. **On rising edge** runs only when that input changes from `false` to `true`. See [Trigger mode](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/configure-rule-chain.md#trigger-mode).
{% endhint %}

A calendar saved with multiple execution times or monthly dates is displayed read-only in this dialog. The dialog indicates when that applies.

## Calendar trigger or Schedule block

The **Calendar** trigger starts the entire chain. The **Schedule** blocks under **Conditions** only return a boolean value when the chain is already executing.

Use a Calendar trigger for a report that must start at a fixed calendar time. Use [Schedule blocks](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/conditions/schedule.md) to permit or block a path during selected hours or weekdays.

Continue with [configuring and connecting the building blocks](https://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/configure-rule-chain.md#add-building-blocks).


---

# 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://docs.buildings.ability.abb/collection/platform/alarms-rules-and-escalations/rule-chains/calendar-trigger.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.
