What is a Message Intermediate Throw Event in BPMN?

A Message Intermediate Throw Event sends a message to an external participant while the process continues execution. It enables mid-process communications without waiting or terminating the flow.

When should I use a Message Intermediate Throw Event?

Use Message Intermediate Throw Events to send notifications, trigger related processes, or update external systems during execution. They enable fire-and-forget communication patterns.

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

Message Throw Events send messages to specific recipients, while Signal Throw Events broadcast to all listeners. Throw events send outward; Catch events receive. Intermediate events occur mid-flow; End events terminate.

What is a Message Intermediate Throw Event in BPMN?

A Message Intermediate Throw Event sends a message to an external participant while the process continues execution. It enables mid-process communications without waiting or terminating the flow.

When should I use a Message Intermediate Throw Event?

Use Message Intermediate Throw Events to send notifications, trigger related processes, or update external systems during execution. They enable fire-and-forget communication patterns.

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

Message Throw Events send messages to specific recipients, while Signal Throw Events broadcast to all listeners. Throw events send outward; Catch events receive. Intermediate events occur mid-flow; End events terminate.

eventsmessage trigger

Message Intermediate Throw Event

A Message Intermediate Throw Event sends a message to an external participant during process execution. It enables processes to communicate with other processes, systems, or users while continuing to execute.

What is a Message Intermediate Throw Event?

A Message Intermediate Throw Event sends a message to a specific external participant while the process continues execution. Unlike End Events, the process does not terminate-it proceeds to the next activity after sending.

Visual Representation

The event displays as a double-line circle containing a filled/solid envelope icon. The filled envelope (vs. unfilled in catch events) indicates outgoing/throwing direction.

Key Characteristics

Outgoing communication: Sends messages to external participants
Non-blocking: Process continues immediately after sending
Targeted delivery: Messages go to specific recipients (unlike broadcasts)
Correlation data: Includes information for recipients to correlate responses

Common Use Cases

Status Notification

Send a "Processing Started" message to the customer while continuing with background processing.

Inter-Process Trigger

Send a message to trigger a related process (invoice generation) while order processing continues.

System Integration

Notify external systems (ERP, CRM) of state changes without waiting for acknowledgment.

Frequently Asked Questions

Try this element in Crismo

Create beautiful BPMN diagrams with our modern process modeling platform.

Open in Editor Browse All Elements