What is a End Event in BPMN?

A None End Event terminates a path of execution in a process. When a token reaches this event, that path ends. The process instance completes when all active tokens have reached End Events.

When should I use a End Event?

Use None End Events to mark normal process completion points. Use multiple End Events to distinguish different outcomes (approved/rejected) or to end parallel paths independently.

How is the End Event different from related elements?

None End Events simply terminate paths with no side effects. Triggered End Events (Message, Signal, Error) perform actions upon termination. Terminate End Events immediately end the entire process instance.

events

End Event

A None End Event terminates a path of execution in the process. When all paths reach End Events, the process instance completes. It represents normal, successful process termination. For example, after an order is shipped and the customer is notified, the process reaches its End Event — all work is done and the instance closes.

What is an End Event?

A None End Event marks the end of a sequence flow path. When a token reaches this event, that path terminates. The process instance completes when all active tokens have reached End Events.

Visual Representation

The End Event displays as a thick-bordered circle that is empty inside. The thick border distinguishes End Events from Start Events (thin border) and Intermediate Events (double border).

Key Characteristics

Path termination: Ends one execution path; other parallel paths may continue
No trigger: Simply terminates the reaching token
Normal completion: Indicates successful, expected process ending
Multiple allowed: A process can have several End Events for different outcomes

See it in action

The shoe ordering process ends with different outcomes

Read: The Shoe Shop →

Common mistake

Using a single End Event for all paths when you should use multiple labeled End Events. Separate End Events for "Approved" and "Rejected" paths make the diagram self-documenting.

How it connects

StartEvery process that begins with a Start Event must end with at least one End Event Terminate EndUse Terminate End Event to immediately kill all parallel paths; None End Event only ends its own path Error EndUse Error End Event when the process path ends due to a failure that needs to be caught upstream Message EndUse Message End Event when the final action is sending a message to another participant Sequence FlowAn End Event has exactly one incoming sequence flow and no outgoing flows

Trigger Variants

End Event can be triggered by different mechanisms.

Message End Event

message trigger

Signal End Event

signal trigger

Error End Event

error trigger

Escalation End Event

escalation trigger

Compensation End Event

compensation trigger

Terminate End Event

terminate trigger

Cancel End Event

cancel trigger

Common Use Cases

Successful Completion

Order processing ends successfully after all items are shipped and customer is notified.

Multiple Outcomes

A request process has separate End Events for "Approved" and "Rejected" paths to distinguish outcomes.

Parallel Path Completion

Each parallel branch ends at its own End Event; process completes when all branches finish.

Frequently Asked Questions

Model this in Crismo

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

Open in Editor Browse All Elements