The following examples demonstrate how sequences and their monitors are able to handle various scenarios.

The situation below shows a monitor firing during the runtime of a sequence.

Monitor checks condition and causes a switch to an exception sequence after which the original sequence is restarted

As soon as a monitor checking for a certain condition fires, an exception sequence is called. The exception must always be blocking. However, it would be possible to omit it altogether. After this the control goes back to the original sequence. How does this sequence now continue? Every monitor can be assigned one of the following properties:

• nothing: the sequence continues normally
• abortOwner: the sequence is aborted and control goes back to its calling sequence
• restartOwner: the sequence gets restarted, its timeout monitor is reset (that's the situation shown in the figure above)
• abortCallerOfOwner:
• restartCallerOfOwner:

The following table shows the behavior for various situations