What is a Escalation End Event in BPMN?

An Escalation End Event terminates a process path while raising an escalation. Unlike errors, escalations signal that attention is needed without necessarily indicating failure.

When should I use a Escalation End Event?

Use Escalation End Events when process completion should trigger attention or handling without implying failure-manual review requests, threshold warnings, priority notifications.

How is the Escalation End Event different from related elements?

Escalation End Events raise attention-seeking signals that may not interrupt; Error End Events indicate failures requiring handling. Escalations are softer; errors are hard exceptions.

What is a Escalation End Event in BPMN?

An Escalation End Event terminates a process path while raising an escalation. Unlike errors, escalations signal that attention is needed without necessarily indicating failure.

When should I use a Escalation End Event?

Use Escalation End Events when process completion should trigger attention or handling without implying failure-manual review requests, threshold warnings, priority notifications.

How is the Escalation End Event different from related elements?

Escalation End Events raise attention-seeking signals that may not interrupt; Error End Events indicate failures requiring handling. Escalations are softer; errors are hard exceptions.

eventsescalation triggerVariant of End Event

Escalation End Event

An Escalation End Event terminates a process path while raising an escalation. Unlike errors, escalations indicate situations needing attention without necessarily indicating failures.

What is an Escalation End Event?

An Escalation End Event ends a sequence flow path and raises a named escalation. Escalation handlers can catch this event to provide handling logic, optionally without interrupting other processing.

Visual Representation

The event displays as a thick-bordered circle containing a filled upward-pointing arrow. The arrow represents the upward escalation to higher attention.

Key Characteristics

Attention signal: Indicates something needs higher-level attention
Non-interrupting option: Handlers can run alongside other processing
Named escalations: Specific codes enable targeted handling
Softer than errors: Indicates attention needed, not necessarily failure

Common Use Cases

Manual Review Required

End automated processing path by escalating to human review when confidence is too low.

Threshold Warning

Escalate to management when process metrics exceed warning thresholds.

Priority Notification

End standard processing and escalate VIP customer requests for expedited handling.

Escalation End Event

What is an Escalation End Event?

Visual Representation

Key Characteristics

Common Use Cases

Manual Review Required

Threshold Warning

Priority Notification

Frequently Asked Questions

Related BPMN Elements

End

Escalation Throw

Try this element in Crismo