BPMN End Events
A BPMN end event marks the point where a path of a process ends. It is drawn as a circle with a thick border. A terminate end event has a filled circle inside and ends the whole process instance at once. BPMN knows two main types:
Reference: BPMN Events shows all event types of the BPMN standard in one table and which ones Flower executes.
- Regular end event: Ends the flow at this point. Parallel branches are not affected.
- Terminate end event: Ends the entire process instance, including all active branches.
How the End Events Work in Flower
Flower follows the standard BPMN behavior and connects it to Jira:
| Regular end event | Terminate end event | |
|---|---|---|
| Effect on the process | Ends only the current flow. Parallel branches continue. | Stops all parallel branches immediately. |
| Process instance work item | Resolved when no branch is running any more | Resolved at once |
| Open task work items | Stay open | Closed |
| Typical use | One path of the process is complete. | The whole process must stop. |
Resolution: When Flower resolves a work item, it also sets the Jira resolution if the workflow does not (Done for the process instance, Won’t Do for the open work items that a terminate end event closes). The field Resolution must be on the transition screen or the edit screen of the work type, or be set by a workflow post function. If it is on none of them, Flower still resolves the work item and writes a warning comment at the process instance. See Sub-Processes and Error and Warning Comments.
Regular End Event
- Ends only the current flow. Parallel branches continue to run.
- The Jira work item of the process instance is resolved when the last branch is done, not when the first branch reaches its end event. Open work items, timers, and gateways that still wait for a branch keep the process instance open.
- Give every branch an end event. A path that ends after its last task without one stops there; the process instance is resolved only if another branch reaches an end event and no branch is still running. The validator warns about such a path.
- To end the process as soon as one branch is done, use a terminate end event.
Terminate End Event
- Stops all parallel branches immediately.
- Flower closes all open work items of the process. Work items that are already resolved stay as they are.
- Flower cancels them: it uses a done status such as Canceled or Rejected if the workflow has one, see Which Status Flower Sets. The process instance itself is resolved as done.
- Closing these work items does not continue the process. The process is terminated for good.
- Running sub-processes end too: Flower closes the open work items of every sub-process, also of nested ones, and then the sub-process itself. A terminate end event inside a sub-process ends only this sub-process, the calling process continues.
When to Use a Terminate End Event
Use it when a business decision stops the process entirely, for example when:
- A project is canceled and all related work must stop.
- A request is rejected and no further steps must run.
- A compliance rule invalidates the process and requires an immediate halt.
With a terminate end event, the work items in Jira show the true status of the process, and no unnecessary work happens.
Example: Job Application Process

In this process, several interviews run in parallel.
- When all interviews are completed successfully, a regular end event is used. Flower resolves the work item of the process instance.
- When one interview fails, the terminate end event stops all other interviews. Flower closes their open work items with a status such as Rejected or Canceled, so the outcome is clear.
If a candidate is rejected in one evaluation, no further assessments are needed. This saves effort, and the process reflects reality.
Frequently Asked Questions
What is an end event in BPMN?
An end event marks the end of a path in a process. It is a circle with a thick border and has no outgoing sequence flow.
What is the difference between an end event and a terminate end event?
A regular end event ends only the path that reaches it, and parallel paths continue. A terminate end event ends the whole process instance immediately, including all parallel paths.
Can a process have more than one end event?
Yes. A separate end event for each outcome, for example Request approved and Request rejected, makes the model easier to read.
Does a terminate end event in a sub-process end the main process?
No. It ends only the sub-process. The calling process continues.
Which other end events does BPMN define?
Message, error, escalation, signal, compensation, cancel, and multiple end events. In Flower, the terminate end event ends the whole process instance, and every other end event ends its flow like the regular one. Two exceptions: an error end event inside a sub-process ends the sub-process with this error (the error boundary event of the call activity or embedded sub-process catches it), and a message end event with a message flow sends its message to the other pool of the model. See BPMN Coverage in Jira.
What’s Next?
- BPMN Events: All event types that Flower supports.
- Set Jira Due Dates with Timer Events: Escalate with timers and end the process on a timeout.
