---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/pt-BR/employee-service-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Modify a scheduled job for Publish Journey Accelerator plans

# Modify a scheduled job for Publish Journey Accelerator plans {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

Update the Publish Journey Accelerator plans job. The job evaluates a plan's
publish date to determine when to publish the plan.

## Antes de Iniciar

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

You can change the scheduled frequency at which the job runs, modify scripts, and add conditions.  
Nota:  
The default scheduled frequency for a Publish Journey Accelerator plan is 12 hours.

## Procedimento

1. Navigate to AllSystem DefinitionScheduled Jobs.
2. In the Name field, enter <kbd class="ph userinput">Publish Journey Accelerator plans</kbd>, press Enter, and then open the job.
3. On the form, fill in the fields.  
   {#ja-schdule-publish-plans__t_ScheduleScriptExecution__entry__2}

   | Field | Description |
   |-|-|
   | Name | Name that identifies this scheduled job. |
   | Active | Option that indicates that scheduled job is active and should be executed at the specified date and time. |
   | Application | Name of the application that contains the script. Global appears if the script is in the global scope. |
   | Conditional | Option for enabling the running of the scheduled job if certain conditions are met in the associated script. |
   | 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. {#ja-schdule-publish-plans__p_nyg_nfg_h1c} * 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. Nota: 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](https://www.servicenow.com/docs/access?context=business-calendars&version=australia&pubname=australia-platform-administration&ft:locale=en-US) and [Define business calendar entries](https://www.servicenow.com/docs/access?context=define-business-calendar-entries&version=australia&pubname=australia-platform-administration&ft:locale=en-US). {#ja-schdule-publish-plans__ul-run-sched-job} |
   | Repeat Interval | 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 <kbd class="ph userinput">04</kbd> in the Days field. * To run it every 26 hours, enter <kbd class="ph userinput">26</kbd> in the Hours field. * If it should repeat at an interval of 13:30:25, enter <kbd class="ph userinput">13</kbd> in the Hours field, and then enter <kbd class="ph userinput">30</kbd> and <kbd class="ph userinput">25</kbd> in the two unlabeled fields after it. {#ja-schdule-publish-plans__ul_bmk_m2b_njb} |
   | 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: |
   | Condition | A conditional script that determines if a scheduled job should run. The last expression of the script should evaluate to a Boolean (true/false) value. This text box appears only if you select Use conditions. |
   | Run this script | Name of the script to run at the scheduled date and time. Two examples are copy script logic from a business rule or call a script include. |
   [Tabela 1. Schedule script execution form]

   {#ja-schdule-publish-plans__t_ScheduleScriptExecution}
4. Click Update.  
   To learn more about scheduled jobs, see [Scheduled
   jobs](https://www.servicenow.com/docs/access?context=c_ScheduledJobs&version=australia&pubname=australia-platform-administration&ft:locale=en-US).