Executing Schedules

As a developer and object designer, after defining a Schedule object you must first activate it manually. The status of the Schedule is then Active. It will execute the first task as soon as all the required conditions are met considering the Schedule Period Turnaround Time and Period Duration as well as the Start Time and Calendar Condition of each task.

This page includes the following:

How Tasks in a Schedule are Processed

When the Schedule is activated, it checks the start times of all its tasks. There are two possibilities:

The start time of a task is in the future

The status of the task is set to Waiting for start time. When the Scheduled time arrives, the task is initiated.
The start time of a task lies in the past

The status of the task is set to ENDED_TIMEOUT -Start time exceeded. You have to reset it; as a result, it executes immediately.

When tasks start, all conditions and dependencies (Calendars, Sync objects, and so on) are checked. The tasks start or do not start depending on the results of these checks and the status of the tasks is set accordingly. For more information, see What Happens when the Tasks Are Activated?.

During their execution, the runtime of the tasks in the Schedule is monitored. This information allows you to react as needed if the runtimes are not what you expect.

Monitoring and Modifying the Schedule

When a Schedule object is executed for the first time, the following happens:

The status of the Schedule is set to Active
The Schedule is visible in the list of tasks in the Process Monitoring perspective
Its monitor is available and provides real-time information about the status of the Schedule and of its tasks

In the Schedule monitor you can change some of the properties of the Schedule object and of its tasks that apply to the current execution.

For more information, see:

Changes to the task and task properties that you make directly in the Schedule can also be passed on to the next period turnaround. Note that in this case, it is not required to restart the schedule. You can also start tasks immediately, regardless of their current states, start times or start conditions.

You can check the status of tasks that are stored in a Schedule object in the Process Monitoring perspective and modify their definitions.

Execution Data

With each period turnaround, a new runID is assigned to the Schedule. This means that each period defined for a Schedule has its own list of Execution Data .

Restarting an Active Schedule

You can restart an active Schedule at any time. You do it in the Process Assembly perspective.

To Restart an Active Schedule

Depending on where you are working, do one of the following:

In the Process Monitoring perspective, do one of the following:
- On the Tasks list, right-click the Schedule and select Source Object > Open Object
- In the Schedule monitor, expand the Modify Schedule buttons and select Source Object > Open Object
In either case, the Schedule object definition pages open up in the Process Assembly perspective.

Expand the Execution Options button on the toolbar and select Restart.
In the Process Assembly perspective right-click the object and select Execution Options > Restart.

Stopping an Active Schedule

Schedules can stop in two different ways:

Manually

You can stop an active Schedule at any time from the Process Monitoring perspective:
- On the Tasks list, right-click the Schedule and select either Suspend or Suspend (recursive).
- In the Schedule monitor, expand the Modify Schedule buttons and select either Suspend or Suspend (recursive).
If you select Suspend, no further tasks are started.

If you select Suspend (recursive), the tasks that are still running will be stopped. In active Workflows, tasks that are still running will continue running but all subsequent tasks will be stopped.
Automatically 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.

Checking Schedules on Start

In rare situations, it might be necessary to restart the Automation Engine. When the Automation Engine starts, it checks whether an active turnaround period took place in the past. If that is the case, it will run as many periods as necessary until it reaches the first one in the future. Only then it checks again whether there are scheduled tasks with a start time in the past. If there are any, their status is set to ENDED_TIMEOUT -Start time exceeded.