---
title: "Schedule Time-Based Automation (window)"
slug: "schedule-time-based-automation-window"
updated: 2024-03-06T09:50:55Z
published: 2024-03-06T09:50:55Z
canonical: "docs.mapp.com/schedule-time-based-automation-window"
---

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

# Schedule Time-Based Automation (window)

The fields in this window define the schedule when a time-based automation is executed. This can be a one-time execution or a repeated schedule.

For more information, see [Time-Based Automation​s](/v1/docs/time-based-automations).

## Basic Settings​

| **​Name​** | The name is used to identify the automation in the system. It appears on the ​Time-based Automations Overview​ window. The maximum length is 100 characters. |
| --- | --- |
| **​Description​** | The description makes it easier to identify the automation in the system. |
| **​Job​** | This input field defines the job. For a list of all available jobs, see [All Available Time-Based Jobs​](/v1/docs/all-available-time-based-jobs). |

## Schedule

- **Time Zone**: Defines the time zone of the automation.
- **Start Date**: Defines the date and time when the automation is activated.
- **Repetition**: These fields define whether the execution takes place on a one-time or recurring schedule.
  - **No**: This option defines that the job is executed only once. In this case the ​Start Date​ is the execution date.
  - **Yes**: This option defines that the job is executed repeatedly, at set intervals. In this case the ​Start Date​ is the first execution date.
  - **Period**: Defines the period of recurrence. The period can be set in hours, days, weeks or months.
  - **Value**: Defines the length of time between recurrences. Example: to execute the automation once every two weeks, enter ​Period:​ ​Week(s)​ and ​Value:​ ​2​.
  - **End Date**: This input field defines the date and time when the automation is deactivated. An automation runs for a maximum of 5 years.
  - **Delete After Last Execution**: Defines whether the automation is deleted after the last execution.

## Advanced Options​

- **Execution Days**: These checkboxes define the days of the week on which the job is executed. The system skips unchecked days and executes the job on the following day.
- **Holidays**: Defines whether the job runs on holidays.
  - **Always**: The job runs whenever it is scheduled. Holidays are not considered.
  - **Never on Holidays**: The job runs never runs on holidays. If the job is scheduled on a holiday, the system delays execution until the next non-holiday.
  - **Only on Holidays**: The job runs only on holidays. If the job is scheduled on a non-holiday, the system delays execution until the next holiday.
  - **Country**: This drop-down field defines the country whose holidays are considered.

## Notification

**Remind Before Deactivation**: These radio buttons define whether a reminder email is sent before the automation is deactivated on the end date. The system message ​SysMsgRemindTriggerExpires​ is sent to the defined addresses 30 days prior to the ​End Date​.

- **Yes**: An additional entry field appears selecting email addresses for notification. Click the ​**Add**​ button to add email addresses. Reminders can only be sent to registered CEP system users. You can add up to 10 addresses.
- **No**: No reminder is sent before the automation expires.

> Automations must be activated as well as saved. Only activated automations are executed by the system. See [Activate a Time-Based Automation​](/v1/docs/activate-a-time-based-automation)).