The next step in scheduling
Documentation flow
Scheduler tasks can be combined in a flow.
A flow is a chain of tasks in which each
task is activated (or not) when
a previous task is ready with a
certain status.
The next flow actions are possible for a
scheduler task after the previous
scheduler task it depends on is ready.
| Activate | Activate the scheduler task. |
| Pass | The scheduler task is not activated but gets the status Passed. |
| Error | The scheduler task is not activated but gets the status Error. |
| Wait |
Do not activate the scheduler task but
wait until a scheduler user changes
the flow action.
The scheduler task gets the task not activated Flow status. |
For each scheduler task status when a task is ready
one of the above four flow actions is set.
If the flow action is not set the default flow action is assumed.
| Finished | The default flow action is Activate. |
| Error | The default flow action is Error. |
| Unknown | The default flow action is Error. |
| Passed | The default flow action is Pass. |
Create flow
On the script submit window (flow panel) the scheduler task flow properties are set.
Wait for task
The flow task identifier this task must be waiting on.
Reschedule
If set this scheduler task is also rescheduled when the previous flow task is rescheduled.
Restart
If set this scheduler task is also restarted when the previous flow task is restarted.
Finished
The flow action if the flow task has status Finished.
Error
The flow action if the flow task has status Error.
Pass
The flow action if the flow task has status Passed.
Unknown
The flow action if the flow task has status Unknown.
Days Hours Minutes Seconds
The sum of these values incremented with the schedule date of the very first flow task is the new schedule date of this task.
Because a flow task can only be activated after the task it depends on is ready the following task properties are ignored on the script submit window (schedule panel).
| schedule_date |
| schedule_till |
| schedule_shift_days |
| schedule_maximum_tasks |
| schedule_keep_days |
| schedule_next_if_error |
| schedule_historical |
| schedule_precreate_tasks |
The next panels are entirely disabled.
- script submit window (days of the week panel)
- script submit window (months panel)
- script submit window (days of the month panel)
- script submit window (weeks panel)
- script submit window (repeat panel)
Flow example
In the next example a flow is created consisting of three tasks. The second task will be activated immediatly after the first task is finished. The third task is activated after the seconds task is finished and is scheduled 2 minutes after the first task is scheduled.
The first scheduler task has got id 383874, this id is used to link the second scheduler task with the first task.
The second scheduler task gets id 383875,
we use this id to link the third task
with the second task.
Also we define a two minutes period; the third task is scheduled two minutes after the first task.
How the flow looks like can be seen on the task tree window.
The letter F indicates that the task is part of a flow.
Back to top