What is a Multiple Intermediate Catch Event in BPMN?

A Multiple Intermediate Catch Event pauses a process until any one of several defined triggers occurs. Using OR semantics, the first trigger to fire resumes the process-others are cancelled.

When should I use a Multiple Intermediate Catch Event?

Use Multiple Intermediate Catch Events when a process should continue on whichever event happens first-response or timeout, approval from any channel, or competing external events.

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

Multiple Intermediate Catch Events fire on ANY trigger (OR), while Parallel Multiple Intermediate Catch Events require ALL triggers (AND). Multiple events model racing alternatives; Parallel events model required synchronization.

What is a Multiple Intermediate Catch Event in BPMN?

A Multiple Intermediate Catch Event pauses a process until any one of several defined triggers occurs. Using OR semantics, the first trigger to fire resumes the process-others are cancelled.

When should I use a Multiple Intermediate Catch Event?

Use Multiple Intermediate Catch Events when a process should continue on whichever event happens first-response or timeout, approval from any channel, or competing external events.

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

Multiple Intermediate Catch Events fire on ANY trigger (OR), while Parallel Multiple Intermediate Catch Events require ALL triggers (AND). Multiple events model racing alternatives; Parallel events model required synchronization.

eventsmultiple trigger

Multiple Intermediate Catch Event

A Multiple Intermediate Catch Event pauses process execution until any one of several defined triggers occurs. It waits for the first of multiple possible events with OR semantics.

What is a Multiple Intermediate Catch Event?

A Multiple Intermediate Catch Event waits for any one of several triggers to occur. When the first trigger fires, the process resumes-it does not wait for all triggers (OR semantics).

Visual Representation

The event shows a double-line circle containing an unfilled pentagon. The pentagon represents the multiple trigger types that can resume the process.

Key Characteristics

OR semantics: First trigger wins-process resumes immediately
Multiple trigger types: Can combine message, timer, signal, conditional
Race condition handling: Explicitly models "whichever comes first" scenarios
Cleaner than gateways: More compact than event-based gateway patterns

Common Use Cases

Response or Timeout

Wait for either customer response message or 48-hour timeout-whichever occurs first.

Multi-Channel Input

Wait for approval via email, mobile app, or web portal-any channel response continues the process.

Competitive Events

Wait for either market signal or scheduled time, processing whichever trigger arrives first.

Frequently Asked Questions

Try this element in Crismo

Create beautiful BPMN diagrams with our modern process modeling platform.

Open in Editor Browse All Elements