If you want to know, what will run today, what should run but did not or was late, you can use the Workplan view in JID.
The JID (JobScheduler Information Dashboard) provides an overview of the jobs planned and those that have successfully been completed.
JobScheduler calculates the start times of jobs and job chains and starts them at the appropriate time.
JobScheduler only considers the start times of the next job or job chain/order and does not consider jobs or orders whose start times lie in the past. However, in everyday job scheduling activities, a calender function or work plan is often useful. JID provides such a plan and provides answers to the following questions:
- what should have run and what has actually run?
- what will run in the next few days?
A particularly useful feature of work plans is that they provide a list of all the jobs and orders that are scheduled to start. In addition, plans are regularly updated to show the current status of jobs or orders. This means that work plans can be used to provide a quick overview of which jobs and orders have run and which have not, and whether jobs that have been completed ran punctually and have been successful.
Please note: JobScheduler will run without any restrictrions if you disable the workplan feature. Only the view in JID with the work plan will be empty.
The data for the workplan will be generated by two jobs:
- The job CreateDailySchedule to create the workplan. This job runs once a day
- The job CheckDailySchedule to look, wether a planned job did run and when.
The job CreateDailySchedule creates a daily schedule for the given intervall (see parameter dayOffset). Before creating the daily schedule, old entries will be deleted. The job creates entries with a planned start time for orders and jobs. Start times with a repeat interval are recorded with one start time for the begin of the interval. Planned start times coming from orders in a setback loop will not be considered. The daily schedule is recorded in the database table DAYS_SCHEDULE
The job looks for each planned entry in the daily calendar a matching entry in the history tables of JobScheduler. The job should be startet with a interval.
The job CheckDaysSchedule looks in the given period. Is no period specified, the job looks in entries for the actual day (see parameter dayOffset). An entry in the history tables will not be assigned more than one time.
The entries will be assigned in ascending order on the starting time (old entries first).
The result of this will be shown in JID (JobScheduler Information Dashboard). It has no effect on the scheduling of jobs in JobScheduler. With other words. If you delete the jobs, everything will work instead of the view of the daily plan in JID.