End Event

Intro

An end event in BPMN marks where a process path stops, with no outgoing sequence flow. It matters because clear endings improve lifecycle control and integration behavior.

Key points:

• Indicates completion or termination results.
• Has result markers such as message, error, compensation, signal, link, or multiple.
• Common use cases: successful completion (BPM), error signaling to callers (Apps/Tech).
• Pitfall: missing end events causing dangling paths.

Examples:

• “Order fulfilled” end event with a message to downstream systems.
• Error end event to trigger compensation in a parent process.
• Signal end event to notify parallel flows.

In practice:

Use explicit end events for each outcome and document the result semantics for integrations.

Related terms: start-event; intermediate-event; sequence-flow

FAQs:

Q: Can a process have multiple end events?
A: Yes, to represent different outcomes.

Q: Do end events send messages by default?
A: Only if configured with a message result.

‍