As the name implies, the End Event indicates where a process will end. In terms of Sequence Flow, the End Event ends the flow of the Process, and thus, will not have any outgoing Sequence Flow. No Sequence Flow can connect from an End Event.

There are nine (9) types of End Events in BPMN: None, Message, Escalation, Error, Cancel, Compensation, Signal, Terminate, and Multiple. These types define the consequence of reaching an End Event. This will be referred to as the End Event Result.

Marker	Description
	The modeler does not display the type of Event. It is also used to show the end of a Sub-Process that ends, which causes the flow to go back to its Parent Process.
	This type of End indicates that a message is sent to a participant at the conclusion of the Process.
	This type of End indicates that an Escalation should be triggered. Other active threads are not affected by this and continue to be executed. The Escalation will be caught by a Catch Escalation Intermediate Event with the same escalationCode or no escalationCode which is on the boundary of the nearest enclosing parent activity (hierarchically). The behavior of the process is unspecified if no activity in the hierarchy has such an Escalation Intermediate Event.
	This type of End indicates that a named Error should be generated. The Error will be caught by the Error intermediate event with the same ErrorCode or no ErrorCode which is on the boundary of the nearest enclosing parent activity (hierarchically). The behavior of the process is unspecified if no activity in the has such an Error intermediate event. The system executing the process may define additional Error handling in this case, a common one being termination of the process instance.
	This type of End is used within a Transaction Sub-Process. It will indicate that the Transaction should be cancelled and will trigger a Cancel Intermediate Event attached to the Sub-Process boundary. In addition, it will indicate that a Transaction Protocol Cancel message should be sent to any Entities involved in the Transaction.
	This type of End indicates that a Compensation is necessary. If an activity is identified, then that is the activity that will be compensated. Otherwise, all activities that have completed within the Process, starting with the top-level Process and including all Sub-Processes, are subject to compensation, proceeding in reverse order. To be compensated, an activity MUST have a Compensation Intermediate Event attached to its boundary.
	This type of End indicates that a Signal will be broadcasted when the End has been reached. Note that the Signal, which is broadcast to any Process that can receive the Signal, can be sent across Process levels or Pools, but is not a Message (which has a specific Source and Target).
	This type of End indicates that all activities in the Process should be immediately ended. This includes all instances of Multi-Instances. The Process is ended without compensation or event handling.
	This means that there are multiple consequences of ending the Process. All of them will occur (e.g., there might be multiple messages sent). The attributes of the End Event will define which of the other types of Results apply.