About adjournment and resumption

Some chains of event actions must be temporarily stopped while waiting for some condition to be met. For example, a customer order needs a manager’s approval before the order can be entered into the system. In this case, the application temporarily halts the execution of the event handler chain until the manager responds with an approval. This event operation is known as adjournment.

Adjourning actions must wait for an external stimulus before the event handler can proceed with the next action. An event handler that contains such an action must be either asynchronous or part of a framework event that can be suspended and is marked to suspend.

When execution reaches an adjourning action, the event handler state is set to retest or time out at a specified time. At this point, the application event becomes an adjourned event.

The event service then processes the application event at the next opportunity after the Time Out or Retest time, or both. This event operation is called resumption.