What is a Message Intermediate Catch Event in BPMN?

A Message Intermediate Catch Event pauses an active process until a specific message is received from an external source. The process resumes execution when the awaited message arrives and correlates to the instance.

When should I use a Message Intermediate Catch Event?

Use Message Intermediate Catch Events when your process needs to wait for external input-approval responses, payment confirmations, callback notifications. They create explicit wait points for inter-process communication.

How is the Message Intermediate Catch Event different from related elements?

Message Intermediate Catch Events pause running processes to wait, while Message Start Events create new instances. Message Throw Events send messages out; Catch Events receive them in.

eventsmessage trigger

Message Intermediate Catch Event

A Message Intermediate Catch Event pauses process execution until a specific message is received. It enables processes to wait for external communications before continuing to the next activity.

What is a Message Intermediate Catch Event?

A Message Intermediate Catch Event suspends a running process until a matching message arrives from an external participant. Unlike Message Start Events which create instances, intermediate events pause existing instances.

Visual Representation

The event displays as a double-line circle (indicating intermediate position) containing an unfilled envelope icon. The double border distinguishes it from start/end events, and the envelope indicates message reception.

Key Characteristics

Wait state: Process execution pauses until the message arrives
Correlation: Messages are matched to waiting instances using correlation keys
Timeout patterns: Often combined with timer events for timeout handling
External integration: Receives messages from other processes, systems, or participants

Common mistake

Not correlating the message to the correct process instance. In multi-instance scenarios, messages must carry a correlation key (e.g. order ID) to reach the right waiting instance.

How it connects

Message ThrowThrow events send messages out; Catch events wait for messages to arrive — they form pairs Receive TaskReceive Tasks also wait for messages but as activities with potential assignment and completion tracking Event GatewayMessage catch events can follow event-based gateways to race against timers or other events Message StartMessage Start Events create new instances; Message Intermediate Catch Events pause existing instances

Common Use Cases

Approval Response

After sending an approval request, the process waits for the approval or rejection message before continuing.

Payment Confirmation

The order process pauses after payment initiation, waiting for bank confirmation message.

External Callback

After calling an async API, the process waits for the webhook callback message with results.

Frequently Asked Questions

Model this in Crismo

Create BPMN diagrams with AI assistance. Free, no signup needed.

Open in Editor Browse All Elements