> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/workflow-framework/workflow-framework-task-execution.md).

# Workflow Framework: Task Execution

Whenever a task is started the system executes it in the following sequence:

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-fcd0aa48dfb729a3604d09b44cccbcc3e36f8203%2Fea476405-54e3-442e-83af-5bbc45f13e25.png?alt=media)

The system first loads the task from the *generic\_task* table and then executes the task using multiple sub-steps:

1. When configured, the system calls the load logicnet to load data into the data context. If load is not configured the framework will load the *dataobject\_data* BLOB from the *generic\_task\_storage* table.
2. When configured, the system triggers the *pre-process* logicnet. It then triggers the *task* logicnet.
3. When configured, the system will trigger the *post-process* logicnet to process data submitted in the *task* logicnet.
4. If the task is a UI task and the selected output option validation is set to "yes", the system will trigger the *validation* step to look for input errors and will display validation warnings if necessary. It will also return to the *task* logicnet. Depending on the selected output, the workflow will remain in the current task or continue to the next task.
5. Finally, when configured, the system calls the *save* logicnet. If the save logicnet is not configured the system will save *dataobject\_data* to the *generic\_task\_storage* table. You can override this behavior with a custom *save* logicnet.

The system will check to determine if the workflow has reached its end. If so, the system will determine if the workflow is a child to another workflow and will trigger the parent workflow.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/workflow-framework/workflow-framework-task-execution.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.