# End

The **End Event** defines the **termination point** of a business process.\
It marks the point at which a process instance **completes its execution and stops**.

In ONEWEB **Process Designer**, the End Event is typically triggered **manually by process flow logic**, indicating that all required activities have finished and no further steps will be executed.

***

### Purpose of End Event

The End Event is used to:

* Explicitly **terminate a process instance**
* Define a **clear completion point** for the workflow
* Indicate successful or logical completion of a business process
* Ensure that system resources associated with the process are released

Every execution path in a process should eventually lead to an End Event.

***

### Characteristics of End Event

* Represents the **final state** of a process
* Stops further execution of activities
* Can appear multiple times in a process to represent different termination scenarios
* Each End Event may represent a distinct business outcome

***

### Usage Guidelines

* A valid process must have **at least one End Event**
* All possible execution paths should terminate at an End Event
* Multiple End Events can be used to represent:
  * Different business outcomes
  * Success and alternative completion paths
* Use descriptive naming when multiple End Events are present to clarify intent
* Avoid placing logic after an End Event, as execution stops at this point

***

### Summary

The **End Event** defines how and when a business process **comes to completion**.

Key points:

* Marks the termination of a process instance
* Mandatory for a complete and valid process design
* Ensures clean and predictable workflow execution
* Can be used multiple times to represent different outcomes

Correct use of End Events ensures that processes in **ONEWEB Process Designer** are **well‑structured, complete, and execution‑safe**.


---

# Agent Instructions: 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:

```
GET https://docs.onewebstack.com/designer-reference/process-designer/process-designer-component/event/end.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.