An event schedule defines points in time when a specific action shall be triggered. Event schedules are used in different parts of the Application Server. For example stored job definitions can define event schedules that specify when a job shall be triggered from a stored job definition.

An Event Schedule consist of event definitions for discrete and recurring events. Discrete event definitions are user defined date&time values that define when and event shall be triggered. Recurring events definitions do not define discrete date&time values but define a scheme for regularly repeated events. The actual points in time when the event schedule triggers events are calculated by evaluating the recurring event definition and adding the discrete events.

Event schedules are precise to the minute, i.e. you can schedule events with a maximum precision of a minute. However the actual execution of the action associated with an event schedule might be delayed (e.g. depending on the system load).

Each event schedule is defined in a specific Time zone, i.e. all data & time values used in the definition of an event schedule are taken as date & time values in that time zone. The same Application Server can handle Event Schedules using Different Time zones.

An Event Schedule can be active or inactive. By deactivating an Event Schedule you can prevent triggering of actions while leaving the definition itself untouched.