> For the complete documentation index, see [llms.txt](https://docs.oneweb.tech/oneweb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oneweb.tech/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/process-components/process-instance.md).

# Process Instance

**Process Instance** is a specific instance of process that is currently executed by a process runtime. Whenever the process is initiated, a corresponding process instance has to be created and started. The process instance contains the Business Object (BO) parameters needed for the activity tasks in the process to achieve the goal of the task. When the process instance is started successfully, the Task Instance of the process instance is created automatically for the first activity task encountered by the process instance.

**Task Instance** is a specific instance of the activity task which is represented by a node task in the Process Designer. A Process Instances can consist of several Task instances. Each task instance has a UUID (Universally Unique IDentifier) that is generated by the process runtime. While the task instance is getting executed on the process instance, this task instance will contain the state of the node task at that given point in time. The potential states are:

**Waiting:** A task instance is waiting for the process runtime to assign the task to a user. \
**Assigned:** A task instance is already assigned to the specific user. \
**Claim:** A task instance is currently worked on by the specific user.

For more details on starting and debugging the process instance, please refer to section [**Process Test & Debug Guideline**](/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/process-test-and-debug-guideline.md)


---

# 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://docs.oneweb.tech/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/process-components/process-instance.md?ask=<question>&goal=<endgoal>
```

`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.