Conditional Intermediate Catch Event
A Conditional Intermediate Catch Event pauses process execution until a specified business condition becomes true. It enables processes to wait for data state changes before continuing.
What is a Conditional Intermediate Catch Event?
A Conditional Intermediate Catch Event suspends a running process until a boolean condition expression evaluates to true. The process engine monitors the condition and resumes execution when satisfied.
Visual Representation
The event shows a double-line circle containing a lined page/document icon. This represents the rule or condition being monitored during the wait.
Key Characteristics
- Expression monitoring: Evaluates boolean expressions against process/business data
- State-driven: Waits for data to reach a specific state
- Polling or reactive: Engine checks conditions periodically or on data changes
- Flexible conditions: Can monitor any accessible data source
Common mistake
Confusing conditional catch events with exclusive gateways. Gateways evaluate conditions once and route immediately; conditional events wait and block until the condition becomes true.
How it connects
Common Use Cases
Threshold Monitoring
An alert process waits until temperature readings exceed safety thresholds before triggering emergency protocols.
Dependency Resolution
A deployment wait until all prerequisite services report healthy status before proceeding.
Document Completion
Approval process pauses until all required documents have been uploaded to the case.
Frequently Asked Questions
Related BPMN Elements
Model this in Crismo
Create BPMN diagrams with AI assistance. Free, no signup needed.