Further define the schedule of a job

In this topic, you learn how to further define the schedule of a job after creation.

Prerequisites

Go to the Schedule tab.
In Maximum Runtime in Seconds Where 0 is No Limit, enter the maximum amount of seconds the job can run for before the job is canceled.
If necessary, to automatically restart the job using a fresh execution context after it has been aborted once the maximum runtime has been reached, select Immediately Restart Job after Abort on Maximum Runtime.

Example: If you have created a data synchronization job to pull records from external APIs and update internal databases, network latency or increased data volume could cause a job to exceed the maximum runtime limit set for it and get aborted by the scheduler. This can lead to stale data. If you select the setting, you start the job immediately after it has been aborted, minimizing downtime, and ensuring retrieval of up-to-date data.
If necessary, to start a job only at a next scheduled interval, select Start Job in Next Interval with Reset after Job Execution.

Example: You want to create a job that compiles transaction data on a regular basis (for example, daily). If you select the setting, you ensure that once a previous job has finished, the system waits until the next scheduled time to run the job again. Any job-related state is reset after previous job execution, ensuring that the next job run starts cleanly.

You have further defined the schedule for the running of a job to correspond to specific business requirements.