What is a Error Start Event in BPMN?

An Error Start Event begins an event sub-process when a specific error is thrown within the parent process. It catches named errors and allows structured exception handling with dedicated recovery logic.

When should I use a Error Start Event?

Use Error Start Events in event sub-processes to handle anticipated exceptions-payment failures, API errors, validation issues. They provide cleaner error handling than complex gateway-based error paths.

How is the Error Start Event different from related elements?

Error Start Events catch thrown errors within event sub-processes, while Error End Events throw errors to be caught. Error Boundary Events attach to activities to catch their errors locally.

What is a Error Start Event in BPMN?

An Error Start Event begins an event sub-process when a specific error is thrown within the parent process. It catches named errors and allows structured exception handling with dedicated recovery logic.

When should I use a Error Start Event?

Use Error Start Events in event sub-processes to handle anticipated exceptions-payment failures, API errors, validation issues. They provide cleaner error handling than complex gateway-based error paths.

How is the Error Start Event different from related elements?

Error Start Events catch thrown errors within event sub-processes, while Error End Events throw errors to be caught. Error Boundary Events attach to activities to catch their errors locally.

eventserror triggerVariant of Start Event

Error Start Event

An Error Start Event initiates an event sub-process when a specific error is thrown within the parent process. It enables structured error handling by catching named errors and executing recovery logic.

What is an Error Start Event?

An Error Start Event is used exclusively within event sub-processes to catch errors thrown by activities in the parent process. When a matching error occurs, the event sub-process activates to handle the exception.

Visual Representation

The Error Start Event shows a thin circle containing a lightning bolt icon. This symbol indicates error or exception handling, distinguishing it from normal flow events.

Key Characteristics

Event sub-process only: Can only be used as the start event of an event sub-process
Named error matching: Catches specific error codes/names thrown by activities
Interrupting behavior: Typically interrupts the normal flow to handle the error
Error propagation: Uncaught errors propagate up the process hierarchy

Common Use Cases

Payment Failure Handling

When a payment transaction throws an error, an event sub-process starts to attempt retry logic or alternative payment methods.

Integration Error Recovery

API call failures trigger an error handler that logs the issue, notifies support, and queues for manual retry.

Validation Error Processing

Data validation errors activate a sub-process that collects all errors and returns them to the user for correction.

Frequently Asked Questions

Try this element in Crismo

Create beautiful BPMN diagrams with our modern process modeling platform.

Open in Editor Browse All Elements