{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":11938,"path":"employee-service-management/journey-accelerator/ja-schdule-publish-plans.md","title":"Modify a scheduled job for Publish Journey Accelerator plans","bundle":null,"doc_type":null,"release":"australia","body":"\n# Modify a scheduled job for Publish Journey Accelerator plans\n\nUpdate the Publish Journey Accelerator plans job. The job evaluates a plan's publish date to determine when to publish the plan.\n\n## Before you begin\n\nRole required: admin\n\n## About this task\n\nYou can change the scheduled frequency at which the job runs, modify scripts, and add conditions.\n\n**Note:** The default scheduled frequency for a Publish Journey Accelerator plan is 12 hours.\n\n## Procedure\n\n1.  Navigate to **All** &gt; **System Definition** &gt; **Scheduled Jobs**.\n\n2.  In the **Name** field, enter `Publish Journey Accelerator plans`, press **Enter**, and then open the job.\n\n3.  On the form, fill in the fields.\n\n<table id=\"t_ScheduleScriptExecution\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nName that identifies this scheduled job.\n\n</td></tr><tr><td>\n\nActive\n\n</td><td>\n\nOption that indicates that scheduled job is active and should be executed at the specified date and time.\n\n</td></tr><tr><td>\n\nApplication\n\n</td><td>\n\nName of the application that contains the script. **Global** appears if the script is in the global scope.\n\n</td></tr><tr><td>\n\nConditional\n\n</td><td>\n\nOption for enabling the running of the scheduled job if certain conditions are met in the associated script.\n\n</td></tr><tr><td>\n\nRun\n\n</td><td>\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</td></tr><tr><td>\n\nRepeat Interval\n\n</td><td>\n\nDuration 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</td></tr><tr><td>\n\nStarting\n\n</td><td>\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</td></tr><tr><td>\n\nCondition\n\n</td><td>\n\nA 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**.\n\n</td></tr><tr><td>\n\nRun this script\n\n</td><td>\n\nName 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.\n\n</td></tr></tbody>\n</table>4.  Click **Update**.\n\n    To learn more about scheduled jobs, see [Scheduled jobs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_ScheduledJobs.md).\n\n\n"}}