> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aseeflow.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Terminate Events

A terminate event ends the complete scope it is raised in and all contained inner scopes.

It is useful if you have a parallel token flow in a process and you want to consume all tokens available in the same scope immediately.

A terminate event on process instance level terminates the complete instance. On subprocess level the current scope and all contained processes instances will be terminated.

<div data-bpmn-diagram="../bpmn/event-terminate" />

## Terminate Event Definition

A terminate event is modeled as an end event with an additional definition element to mark the termination:

```xml theme={null}
<process id="someProcess">
  <!-- ... -->
    <endEvent id="EndEvent_2" name="Tweet rejected">
      <terminateEventDefinition id="TerminateEventDefinition_1"/>
    <endEvent>
  <!-- ... -->
</process>
```

## ASEE Flow Extensions

<table class="table table-striped">
  <tr> <th>Attributes</th> <td> [camunda:asyncBefore](/reference/bpmn20/custom-extensions/extension-attributes#asyncbefore), [camunda:asyncAfter](/reference/bpmn20/custom-extensions/extension-attributes#asyncafter), [camunda:exclusive](/reference/bpmn20/custom-extensions/extension-attributes#exclusive), [camunda:jobPriority](/reference/bpmn20/custom-extensions/extension-attributes#jobpriority) </td> </tr>
  <tr> <th>Extension Elements</th> <td> [ camunda:inputOutput](/reference/bpmn20/custom-extensions/extension-elements#inputoutput) </td> </tr>
  <tr> <th>Constraints</th> <td>–</td> </tr>
</table>

### Additional Resources

* [Terminate Events](https://camunda.com/bpmn/reference/#events-termination) in the [BPMN 2.0 Modeling Reference](https://camunda.com/bpmn/reference/)