{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":20314,"path":"integrate-applications/automation-center/auto-sched-trigger-exe-form.md","title":"Automation Scheduled Trigger Execution form","bundle":null,"doc_type":null,"release":"australia","body":"\n# Automation Scheduled Trigger Execution form\n\nUse the Automation Scheduled Trigger Execution form to define the type of insight trigger and map an insight rule to a new scheduled script in Automation Center.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName\n\n\n\nName of the insight trigger.\n\n
\n\nActive\n\n\n\nOption for ensuring the use of the insight trigger.\n\n
\n\nApplication\n\n\n\nThe associated application or the application scope in which the trigger is being created, such as Automation Center or RPA Hub.\n\n
\n\nRun\n\n\n\nTime interval to use for running the scheduled job:\n\n- **Daily**: Runs daily, at a designated time.\n- **Day and Month in Year**: Runs yearly on a specific day and month \\(for example, July 14\\), at a designated time.\n- **Day in Week in Month in Year**: Runs yearly on a specific day of the week in a specific week of a specific month \\(for example, the second Monday in October\\), at a designated time.\n- **Week in Month**: Runs monthly during a specific week of the month \\(for example, the third week of each month\\), on designated days and at a designated time.\n- **Weekly**: Runs on a weekly basis, at a designated time and day of the week.\n- **Monthly**: Runs on a monthly basis, at a designated time and day of the month.\n- **Periodically**: Runs on a designated repeating interval.\n- **Once**: Runs for a single occurrence only.\n- **On Demand**: Runs immediately on demand.\n- **Business Calendar: Entry Start**: Runs on the starting entry dates for the business calendar that you select in the **Business Calendar** field. A scheduled job runs for the starting date of each of the business entries that you defined for the business calendar.\n\nFor example, if the business calendar represents a fiscal year, and the starting date of each entry is a fiscal month, the scheduled job runs on the first day of each month.\n\n- **Business Calendar: Entry End**: Runs for the ending date for the business calendar that you select in the **Business Calendar** field. This selection runs in the same manner as **Business Calendar: Entry Start**, but for the end dates of the associated business calendar entries.\n\n**Note:** When you select **Business Calendar: Entry Start** or **Business Calendar: Entry End**, you can apply an offset factor to schedule the job to run before or after the time span of the selected business calendar. If you select a business calendar and all its business calendar spans are in the past, the job would never run since that is an invalid configuration. To learn more, see the **Offset type** and **Offset** fields.\n\nTo learn more about creating and using business calendars and defining business calendar entries, see [Creating business calendars](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/business-calendars.md) and [Define business calendar entries](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/define-business-calendar-entries.md).\n\n\n
\n\nDay\n\n\n\nDay on which the scheduled job should run.\n\n- If **Run** is set to **Weekly**, select the day of the week. For example, select Wednesday.\n- If **Run** is set to **Monthly**, select the day of the month. For example, select 25 for the 25th day of the month.\n\nThis field appears only if you select **Monthly** or **Weekly** in the **Run** field.\n\n
\n\nRepeat Interval\n\n\n\nThis field appears only if you select **Periodically** in the **Run** field.\n\n Duration of the repeat interval for each scheduled job execution. Enter the duration in the number of days, hours, or minutes. For example:\n\n- To run the scheduled job every four days, enter `04` in the **Days** field.\n- To run it every 26 hours, enter `26` in the **Hours** field.\n- If it should repeat at an interval of 13:30:25, enter `13` in the **Hours** field, and then enter `30` and `25` in the two unlabeled fields after it.\n\n
\n\nTime zone\n\n\n\nTime zone to use with the **Time** field entry when you specify the time at which the scheduled job should run. Select a time zone entry:\n\n- **-None-**: Use the default time zone for the logged-in user who is creating the scheduled job.\n\nFor example, the scheduled job runs at 04:45 p.m. US/Pacific time if it’s the user's assigned time zone, and you enter `16:45` into the **Time** field.\n\n- **Use System Time Zone**: Use the default system time zone that is specified for the instance in which it runs.\n\nFor example, the scheduled job runs at 10:15 p.m. London time if Europe/London is the default system time zone for the instance, and you enter `22:15` in the **Time** field.\n\n- Actual time zone.\n\nFor example, the scheduled job runs at 1:30 p.m. in the US Eastern time zone if you select **US/Eastern**, and enter `13:30` in the **Time** field.\n\n\n
\n\nTime\n\n\n\nTime of day at which the scheduled job should run, expressed in hours, minutes, and seconds on a 24-hour clock. The selection that you make in the **Time zone** field determines the time zone for this entry.\n\n
\n\nStarting\n\n\n\nAllows you to define the beginning window of time when you would like your job to start running. The job will actually run at the time specified in **Run time**. Select the calendar date and time. The **Starting** field appears only if you select one of the following **Run** types in the **Run** field:\n\n
\n\nBusiness Calendar\n\n\n\nBusiness calendar entry that you’re using to determine the business calendar start or end date for the scheduled job. This field appears only if you select **Business Entry: Start Date** or **Business Entry: End Date** in the **Time** field.\n\n
**Parent Topic:**[Automation Center reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/automation-center/automation-center-reference.md)\n\n"}}