A recurring job is used to describe a job that repeats at regular intervals; for example, twice a week, or once a month. Recurring jobs are useful when a job needs to recur on a regular basis, but when the actual day that the job takes place is flexible.
When you create a recurring job, you provide the same basic information that you would for a job, including load information, time windows, drivers, and required or disallowed attributes. However, unlike a job, you do not need to specify a job date. Instead, you choose an interval, the permitted days of the week, a start date, and an end date after which the recurring job ends. If you do not set an end date, the recurring job repeats indefinitely. Although the jobs that are created from this recurring job must still be created for a set date range. Additional jobs can continue to be created in future using the same recurring job.
Once these recurring job values have been specified, a job must be created from the recurring job. This process creates as many jobs as are needed to satisfy the requirements of the recurring job over the specified period. The optimizer determines the best date and time for the jobs needed to meet the demands of the recurring job. Once created, these jobs appear in the Jobs list, and can be assigned to your routes.
Recurring job-related topics in this section:
Creating Recurring Jobs: Adding new recurring jobs to a scenario.
Editing Recurring Jobs: Editing the details of recurring jobs you created previously.
Deleting Recurring Jobs: Deleting recurring jobs from a scenario.
Importing and Exporting Recurring Jobs: Exporting a file that lists all recurring jobs in a scenario, and importing recurring jobs from a file.
Creating Jobs from Recurring Jobs: Creating new jobs from your recurring jobs so that they can be assigned to routes.