Automation Scheduled Trigger Execution form

  • Release version: Zurich
  • Updated July 31, 2025
  • 4 minutes to read
    • Summarize
    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 Automation Scheduled Trigger Execution form

    The Automation Scheduled Trigger Execution form in ServiceNow enables customers to define and schedule insight triggers for automation tasks within Automation Center or RPA Hub. It maps insight rules to scheduled scripts, allowing automated execution based on various time intervals and business calendar configurations.

    Show full answer Show less

    Key Features

    • Name and Activation: Specify the name of the insight trigger and activate it to ensure it is used.
    • Application Scope: Select the application or scope (e.g., Automation Center or RPA Hub) where the trigger is created.
    • Run Time Options: Supports multiple scheduling intervals including:
      • Daily, Weekly, Monthly, Yearly (specific day/month or week/day combinations)
      • Periodic intervals with customizable repeat durations (days, hours, minutes, seconds)
      • Single occurrence (Once) or immediate execution (On Demand)
      • Business Calendar-based scheduling at entry start or end dates, with optional offset adjustments
    • Day Selection: For weekly or monthly runs, specify the exact day of the week or month.
    • Time Zone and Time: Define the time zone context (user default, system default, or specific time zone) and the exact time of day for the scheduled job.
    • Starting Window: Specify a start date and time window when using business calendar-based scheduling to control when the job begins running.

    Practical Use and Considerations

    • Business calendar scheduling is ideal for aligning automation with fiscal or operational calendars; however, ensure calendar entries are current to avoid invalid configurations where jobs would never run.
    • Offset factors can fine-tune scheduling around business calendar dates to run jobs before or after defined entries.
    • Choosing the correct time zone setting ensures the scheduled job executes at the intended local time, critical for global operations.

    What Customers Can Expect

    By configuring the Automation Scheduled Trigger Execution form, customers can automate the execution of insight-driven rules at precise times and intervals that align with business needs and calendars. This facilitates timely and consistent automation workflows with flexible scheduling options, improving operational efficiency and responsiveness.

    Use 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.

    Table 1. Automation Scheduled Trigger Execution
    Field Description
    Name Name of the insight trigger.
    Active Option for ensuring the use of the insight trigger.
    Application The associated application or the application scope in which the trigger is being created, such as Automation Center or RPA Hub.
    Run
    Time interval to use for running the scheduled job:
    • 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.
    • 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.
    • Monthly: Runs on a monthly basis, at a designated time and day of the month.
    • Periodically: Runs on a designated repeating interval.
    • Once: Runs for a single occurrence only.
    • On Demand: Runs immediately on demand.
    • 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.

      For 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.

    • 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.
      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.

      To learn more about creating and using business calendars and defining business calendar entries, see Creating business calendars and Define business calendar entries.
    Day
    Day on which the scheduled job should run.
    • If Run is set to Weekly, select the day of the week. For example, select Wednesday.
    • If Run is set to Monthly, select the day of the month. For example, select 25 for the 25th day of the month.
    This field appears only if you select Monthly or Weekly in the Run field.
    Repeat Interval

    This field appears only if you select Periodically in the Run field.

    Duration of the repeat interval for each scheduled job execution. Enter the duration in the number of days, hours, or minutes. For example:
    • To run the scheduled job every four days, enter 04 in the Days field.
    • To run it every 26 hours, enter 26 in the Hours field.
    • 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.
    Time zone
    Time 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:
    • -None-: Use the default time zone for the logged-in user who is creating the scheduled job.

      For 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.

    • Use System Time Zone: Use the default system time zone that is specified for the instance in which it runs.

      For 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.

    • Actual time zone.

      For 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.
    Time Time 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.
    Starting Allows 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:
    Business Calendar

    Business 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.