> For the complete documentation index, see [llms.txt](https://docs.senpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.senpiper.com/alarm-builder/alarms-for-custom-data-exports/add-a-new-alarm/define-schedule.md).

# Define Schedule

Step 3 of setting up a custom alarm is configuring a schedule for when the alarm should be triggered.&#x20;

<figure><img src="https://4216568905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mc6E3BSGr4i8kVdH38k%2Fuploads%2FZ9vcOawH9NADLEXySd3y%2Fschedule%20custom%20alarm.png?alt=media&amp;token=a9fee30d-ef2a-4aac-8b66-1d246facd398" alt=""><figcaption><p><em>Define Schedule</em></p></figcaption></figure>

We can define a fixed schedule for the alerts to be sent to the user.

1\.    Select the date & time when to initiate the alarm&#x20;

2\.    After selecting the initiation date & time, select the execution of an alarm event - **Once**, or **Repeated.**&#x20;

To send out the data exports at regular intervals, select **Repeated**. On selecting **Repeated**, we will ask to select the time duration after which we want to send out the notifications.&#x20;

{% hint style="info" %}
The alternative way to define a schedule for alerts is by providing a CRON expression. A cron expression is a string comprising a number of fields that represent the individual details of a schedule. For more information on CRON expressions, see <https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm>
{% endhint %}
