There are 3 types of timer events available:
Timer Start Event
Timer Intermediate Event
Timer Boundary Event
The first one is covered in the start events documentation.
Timer Intermediate Event¶
An intermediate timer event acts as a stopwatch. When the execution arrives, a timer is started. After the specified interval, the execution continues.
In this example, task A won’t be executed until the timer has elapsed.
You can set the trigger to work after a specific period of time, or you can set it to run at a specific time.
Timer Boundary Event¶
If you drag a timer intermediate event into a task, you create a timer boundary event.
A timer boundary event is a timer that is attached to another task. It starts running when the execution arrives to its parent task. If the task is not completed before the timer elapses, a new execution path is created from the timer.
If the Cancel Activity option is enabled, when the timer elapses, it cancels the parent activity.
If it’s disabled, a new execution path is created from the timer, but the parent activity remains active.
Multiple Outgoing Sequences from a boundary event¶
If you want to execute multiple activities from a timer boundary event, you must use a gateway as you can see in the following diagram: