What is a Cancel End Event in BPMN?

A Cancel End Event terminates a transaction sub-process and triggers its cancellation. It activates the Cancel Boundary Event and executes compensation handlers for activities completed within the transaction.

When should I use a Cancel End Event?

Use Cancel End Events inside transactions to explicitly cancel and roll back-user-initiated cancellations, validation failures, timeout scenarios. They provide controlled transaction rollback paths.

How is the Cancel End Event different from related elements?

Cancel End Events work only in transactions, triggering compensation via Cancel Boundary Events. Error End Events throw errors that propagate; Terminate End Events kill instances without compensation.

eventscancel triggerVariant of End Event

Cancel End Event

A Cancel End Event terminates a transaction sub-process and triggers its cancellation. It causes the transaction to roll back by executing compensation handlers.

What is a Cancel End Event?

A Cancel End Event is used exclusively within transaction sub-processes to cancel the transaction. Reaching this event triggers the transaction cancellation boundary event and executes compensation for completed activities.

Visual Representation

The event shows a thick-bordered circle containing an X mark. This X represents cancellation of the transaction.

Key Characteristics

Transaction scope only: Can only be used inside transaction sub-processes
Triggers cancellation: Activates the Cancel Boundary Event on the transaction
Compensation execution: Completed activities within the transaction are compensated
Controlled rollback: Provides explicit cancellation path in transaction flows

See it in action

The customer cancels the money transfer mid-process

Read: Bankovia →

Common mistake

Using a Cancel End Event outside a Transaction. Cancel End Events can only appear inside Transaction sub-processes — they have no meaning in regular sub-processes or processes.

How it connects

TransactionCancel End Events can ONLY be used inside Transaction sub-processes to trigger cancellation Compensation EndCompensation reverses completed work; Cancel End Events trigger the transaction cancellation protocol Error EndError End Events signal failures; Cancel End Events signal intentional cancellation by the user or system Terminate EndTerminate End Events kill all parallel paths; Cancel End Events trigger orderly rollback within a transaction

Common Use Cases

Explicit Cancellation

User explicitly cancels a multi-step booking transaction, rolling back all reservations.

Validation Failure Rollback

Final validation fails in transaction, triggering cancel to roll back all committed steps.

Timeout Cancellation

Transaction exceeds allowed time, cancelled to release held resources.

Frequently Asked Questions

Model this in Crismo

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

Open in Editor Browse All Elements