Introduction

The jobs used in Job Streams can have their individual run-times, which changes the execution process of the job in a Job Stream. The run-time of a job can be used to postpone the execution of a job in the Job Stream. There are two possible solutions in which the execution of the job can be postponed in a Job Stream:

  1. Postpone the execution for a later hour within the same day
  2. Skip the execution of the job in a Job Stream

Postpone the execution for a later hour within the same day

The execution of a job in a Job Stream can be postponed for later hours by assigning a Time Slot frequency.  

The job in the Job Stream will only be executed if the execution time for the job is within the Time Slot interval. Otherwise the job is added to the Task Queue for later execution and will be marked as Not In Period.

If we want to limit the period for job execution to two hours, e.g. a job should be executed each day between 14:00 and 16:00, then we can assign a Time Slot frequency to the job with Begin = 14:00 and End = 16:00. Refer to the screenshot for reference.

Skip the Execution of a Job in a Job Stream

To skip the execution of the Job in a Job Stream, assign a working days calendar to the job.

The working days calendar assigned to the job includes frequency of dates on which the job can be executed. 

A job can be skipped by assigning a calendar in two ways:

  1. Create a working days calendar, including dates only for which the job should be executed.



  2. Create a working days calendar with a frequency for every day. Assign the calendar to the job and add a restriction.



If we want to skip the execution of a job in a Job Stream, e.g. from Monday to Friday, then create a working days calendar with a frequency for every day. Assign the calendar to the job and add a restriction for Saturday and Sunday.

When the Job Stream is running Monday to Friday then the job will be skipped for these days due to the restriction to run only Saturday and Sunday. 

Note: If a job is skipped, then the event for the Out Condition is created as if the job completed with exit code 0.



  • No labels