Executing Schedules Documentation is incorrect

Document ID : KB000087464
Last Modified Date : 14/04/2018
Show Technical Document Details
Error Message :

The section describing "Termination or Period Turnaround of a Schedule That Includes Active Tasks" in the Schedule Execution section of the documentation is incorrect.

It should contain the following information when describing what happens when the Execution of a Schedule is stopped.

You can stop and restart an active schedule at any time. If you choose to Suspend it, no further tasks are started. If you go for Suspend (recursive), the tasks that are still running in active workflows will continue running but all subsequent tasks will be stopped.

The execution of a schedule object can stop in two ways with different implications in both cases:
  • Manually, either from the Last Monitor or from the main window in the Process Monitoring perspective, or from the Process Assembly perspective.
    You can right-click the active schedule and select one of the available options that will stop it.
    The schedule is ended immediately. Its tasks are displayed on the Tasks window (Process Monitoring) without their parent task (the schedule).
  • Due to a period turnaround
    If a schedule object is still active and its tasks are being executed when a period turnaround takes place, the following occurs:
    • A new instance of the schedule is created for the new period.
    • The tasks of the old instance that have not finished yet continue running in the new Schedule instance
    • The tasks of the old instance that had already finished are available and displayed on the Tasks list as single tasks; their execution data is still available.

Cause type:
Root Cause: Schedule Execution documentation contains inaccurate information.
Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Component(s): Documentation

Automation Engine 12.0.1 – Available
Automation Engine 11.2.2 - Available
Automation Engine 11.1.3 – Available
Additional Information:
Workaround :