Each stored job definition can optionally define an event schedule. This schedule will then be used by the job scheduler to trigger the execution jobs at defined points in time. Note that due to the load balancing of jobsthe stored job is not necessarily executed exactly at the scheduled point in time but might be delayed.

Each minute the job scheduler checks the all stored job definitions with an event schedule. If the schedule defines a specific job to be run in this minute the job will be triggered by the job scheduler. From that point in time the execution of the job is managed by the job engine.

The job scheduler is started during the startup of the Application Server. If a stored job's event schedule defines triggering a job from a stored job definition for a point in time when the server was down these jobs will not be triggered, i.e. the server does not catch up with work missed during a downtime. You can however use immediate execution to trigger execution of missed jobs.