> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/analystes-de-processus/business-process-management/creating-and-editing-process-diagrams/mapping-a-process/editing-bpmn-properties-for-objects-and-flows/events.md). # Events Configure properties to define the event type, characteristic, and subtype, which determine when and how a process responds. An **event** represents a key occurrence in a process. It may start the process, affect its flow, or bring it to an end. Each event can be defined by: * **Type** — its position and role in the process lifecycle * **Characteristic** — how it behaves when triggered * **Subtype** — the specific trigger or outcome *** ## Event Types Event types define **where** in the process lifecycle the event occurs.

	What It Is	What It Looks Like
Start Event	Marks the beginning of a process.
Intermediate Event	Occurs between the start and end of a process.
End Event	Marks the completion of a process.

{% hint style="info" %} While event types are not BPMN properties themselves, they determine **which properties** are available for configuration. To select an event type, drag the corresponding event shape from the panel into your diagram. {% endhint %} *** ### Event Characteristics Event characteristics define **how** an event behaves when it is triggered. > **Note:** If an event already has incoming or outgoing **sequence flows**, its characteristic cannot be changed. BPMN distinguishes events by two main behavioral characteristics: #### 1. Catching vs. Throwing

	What It Is	What It Looks Like
Catching	A catching event is triggered by an external condition or signal. It waits for something to happen before proceeding. Example: Receiving an email.
Throwing	A throwing event is initiated by the process itself. It does not require an external trigger—it actively causes an action to occur. Example: Sending an email.

What It Is

What It Looks Like

Catching

A catching event is triggered by an external condition or signal. It waits for something to happen before proceeding.

Example: Receiving an email.

Throwing

A throwing event is initiated by the process itself. It does not require an external trigger—it actively causes an action to occur.

Example: Sending an email.

#### 2. Interrupting vs. Non-Interrupting

	What It Is	What It Looks Like
Interrupting	An interrupting event stops the ongoing activity or subprocess when triggered. It is represented with a solid outline.
Non-Interrupting	A non-interrupting event allows the process to continue even after it is triggered. It is represented with a dotted outline.

*** ### Summary — Event Types & Allowed Characteristics The table below shows which event characteristics are available for each event type.

Event Type	Event Characteristic
Start	Catching – Interrupting, Catching – Non-Interrupting
Intermediate	Catching – Interrupting, Catching – Non-Interrupting, Throwing – Interrupting
End	Throwing

*** ## Event Subtypes Event subtypes define the **specific trigger** (for start/intermediate events) or **result** (for end events).

	What It Is	What It Looks Like
Message	A message event represents any type of communication, such as a letter, email, or phone call.
Timer	A timer event represents a specific time or date, such as a countdown, deadline, or scheduled start time.
Escalation	An escalation event indicates that an activity must be raised to a higher authority. It is often used in event subprocesses to signal priority handling.
Conditional	A conditional event represents a situation where a specific condition or rule must be met before the process can continue.
Link	A link event connects sections of a process diagram or links a parent process to a subprocess, replacing sequence flows. It is particularly useful in multi-page diagrams.
Error	An error event represents a problem or fault in the process, allowing for corrective or alternative actions to be taken.
Cancel	A cancel event indicates the termination of a transaction or activity before its completion.
Compensation	A compensation event represents the failure or reversal of an activity that requires reimbursement or corrective action.
Signal	A signal event represents a broadcast notification sent without a specific recipient, making it accessible to multiple participants.
Multiple	A multiple event represents a situation where any one of several possible triggers may initiate the event.
Parallel Multiple	A parallel multiple event represents a situation where several triggers must occur simultaneously to initiate the event.
Terminate	A terminate event immediately ends the process, stopping all ongoing activities regardless of their current state.

*** ### Summary — Event Subtype Availability The table below lists which event subtypes are supported for **Start**, **Intermediate**, and **End** events.

Event Subtype	Start	Intermediate	End
Message	✅	✅	✅
Timer	✅	✅	❌
Escalation	✅	✅	✅
Conditional	✅	✅	❌
Link	✅	✅	✅
Error	❌	✅	✅
Cancel	❌	✅	✅
Compensation	❌	✅	✅
Signal	✅	✅	✅
Multiple	✅	✅	✅
Parallel Multiple	✅	✅	❌
Terminate	❌	❌	✅

*** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/analystes-de-processus/business-process-management/creating-and-editing-process-diagrams/mapping-a-process/editing-bpmn-properties-for-objects-and-flows/events.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.