--- sourceDocument: Brazil ServiceNow AI Platform Administration sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil ServiceNow AI Platform Administration ft:clusterId : - platadm bundleId : - platadm workflow : - Platform --- # Advanced options for scheduled jobs # Advanced options for scheduled jobs {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Advanced options for scheduled jobs Advanced options for scheduled jobs in ServiceNow provide enhanced flexibility in planning and executing jobs. These options allow customers to define specific start and end dates, set precise run times, and configure custom repeat intervals for jobs according to various scheduling needs. Show full answer Show less ## Key Features * **Run Types with Advanced Options:** When a scheduled job's Run field is set to certain values such as Daily, Monthly, Weekly, or Periodically, advanced scheduling fields become available to further customize the job's timing. * **Advanced Scheduling Fields:** * **Starting / Starting (Timezone):** Defines the future window's start time for job execution, either in local user time or a selected time zone. * **Ending / Ending (Timezone):** Defines the future window's end time when the job should stop running. * **Repeat every:** Enables specifying custom recurrence intervals (e.g., every 2 days or every 3 weeks), except for some yearly run types. * **Time Zone Handling:** Starting and Ending fields behave differently depending on whether a time zone is selected: * If a time zone is selected, entered times in the Starting (Timezone) and Ending (Timezone) fields are converted to local time. * If no time zone is selected (set to -- None --), the job runs in the time zone of the user who executes it. * **Scheduling Behavior Example:** A daily job starting June 1 at 00:00 with a run time of 9:00 a.m. and a Repeat every value of 1 runs first at 9:00 a.m. on June 1 within the defined window. Adjusting Repeat every to 2 causes runs every other day within the window until the ending date. ## Practical Guidance for ServiceNow Customers * Use the advanced scheduling options to precisely control when scheduled jobs start, end, and how frequently they run, enhancing automation and workload management. * When selecting a time zone, always enter the Starting and Ending times after setting the time zone to avoid resetting the entered times. * Understand that the Starting and Ending fields create a window during which the job can run, but the actual execution time is determined by the Run time and repeat interval. * Note that some run types (Day and Month in Year, Day in Week in Month in Year) do not support the Repeat every field. Advanced scheduling options for scheduled jobs support greater flexibility in job planning and execution. You can configure jobs to start on a future date, end on a particular date, and define how the job should repeat. When the Run field is set to one of the following values, an Advanced option displays on the scheduled job form: * Daily: Runs daily, at a designated time. * Day and Month in Year: Runs yearly on a specific day and month (for example, July 14), at a designated time. * 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. * Monthly: Runs on a monthly basis, at a designated time and day of the month. * Periodically: Runs on a designated repeating interval. * 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. * Weekly: Runs on a weekly basis, at a designated time and day of the week. {#advanced-options-for-scheduled-jobs__ul_tpb_1yc_mfc} If you select the Advanced option, the following advanced fields display on the form: * Starting or Starting (Timezone): Specifies the beginning of a window in the future within which the job starts running. The Time field determines the actual start time in the window. * Ending or Ending (Timezone): Specifies the ending of a window in the future within which the job stops running. The Time field determines the actual stop time in the window. * Repeat every: Enables custom recurrence patterns. For example, a daily job that repeats every two days or a weekly job that repeats every three weeks. Note: The Repeat every field isn't supported with the Day and Month in Year and Day in Week in Month in Year run types. {#advanced-options-for-scheduled-jobs__ul_lcw_jtx_jfc} ## Starting and Ending fields {#advanced-options-for-scheduled-jobs__section_byj_fjk_cjc} The Scheduled Job \[sysauto\] table has multiple Starting and Ending fields. Each field behaves differently depending on whether a time zone is selected in the Time zone field.{#advanced-options-for-scheduled-jobs__table_vvl_gjk_cjc__entry__4} | Column name | Column label | When used | Behavior | |-|-|-|-| | run_start | Starting | No time zone selected | Stores the value you enter directly. The job starts at the entered time in the time zone of the user who runs the job. By default, the user who creates the job is the user who runs the job. | | entered_run_start | Starting (Timezone) | Time zone selected | Uses the value you enter and the selected time zone to automatically calculate the value of the other Starting \[run_start\] field by converting your entered time to the equivalent local time as displayed in the UI. | | run_end | Ending | No time zone selected | Stores the value you enter directly. The job stops at the entered time in the time zone of the user who runs the job. By default, the user who creates the job is the user who runs the job. | | entered_run_end | Ending (Timezone) | Time zone selected | Uses the value you enter and the selected time zone to automatically calculate the value of the other Ending \[run_end\] field by converting your entered time to the equivalent local time as displayed in the UI. | [Table 1. Starting and Ending field behavior by time zone selection] {#advanced-options-for-scheduled-jobs__table_vvl_gjk_cjc} When setting the Starting and Ending fields, follow these guidelines based on your time zone selection: * Time zone selected: In the Time zone field, select a time zone, and then enter your desired starting and ending times in the Starting (Timezone) \[entered_run_start\] and Ending (Timezone) \[entered_run_end\] fields. The system automatically calculates the values of the other Starting \[run_start\] and Ending \[run_end\] fields. * No time zone selected: In the Time zone field, select -- None --, and then enter your desired starting and ending times in the Starting \[run_start\] and Ending \[run_end\] fields. The job runs in the time zone of the user who runs the job. {#advanced-options-for-scheduled-jobs__ul_wvl_gjk_cjc} Note: If you select a time zone, you must enter the starting and ending times after setting the Time zone field otherwise the times might be reset. ## Daily scheduled job with no time zone {#advanced-options-for-scheduled-jobs__example_pgd_b3k_cjc} The following example of a daily job illustrates the behavior of the Starting, Ending, and Repeat every fields. The daily job has the following schedule: * Starting \[run_start\]: June 1 at 00:00 * Ending \[run_end\]: June 30 at 23:59 * Time: 9:00 a.m. * Repeat every: 1 day {#advanced-options-for-scheduled-jobs__ul_fmq_b3k_cjc} Although the job is scheduled to start on June 1 at 00:00, it doesn't run at that time. Instead, the job first runs at 9:00 a.m. on June 1 because that is the specified run time. The starting and ending times define the window of time during which the job is set to run. The first valid scheduled run within that window is when the job will run, in this case at 9:00 a.m. on June 1. When creating scheduled job records, if the value of the Starting field is empty, the system uses the current time. If you change the value of the Repeat every field to 2, the job runs every 2 days at 9:00 a.m. starting on June 1. That means it runs on June 1, June 3, June 5, and so on, continuing every other day until June 29---the last occurrence before the ending time of June 30 at 23:59. **Related concepts** * [Scheduled jobs](https://www.servicenow.com/docs/cmhdRH0L6oXgLN99T0XaHg "Scheduled Jobs are automated pieces of work that can be performed at a specific time or on a recurring schedule.") **Related tasks** * [Create a scheduled job](https://www.servicenow.com/docs/vPCyfFn_MUhKGHAWc5mMHg "Create a scheduled job on the Schedule Job [sysauto] table.") * [Enable run types for scheduled job child tables](https://www.servicenow.com/docs/znIRgU35Hfo3GN0DStv9Ww#customize-run-times-for-scheduled-jobs "The run types; Day and Month in Year, Day in Week in Month in Year, and Week in Month, require the fields; Day, Month, and Year to be visible. Child tables which don’t display those fields can't create jobs with that run type selected.")