> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemmodeler/flowcharts/async-tasks.md).

# Async Tasks

<figure><img src="/files/bVSHaVwFWXFOEG9W5f3B" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
The Async Task nodes only work in Kubernetes Runtimes v4.2 and up.&#x20;

In current Shared Europe (v3 Windows) or 4.1 kubernetes runtimes, an error will show:\
"The current flowchart node is not supported by this version of the WEM runtime."

When released, we will add screenshots and further information.
{% endhint %}

## Introduction

With the async task nodes you can run tasks in a background process. Async Tasks can be started, stopped and monitored with specific nodes. This can be useful if you want to start long running tasks without having to wait for them to finish. Users can continue their processes and work while the Async Tasks work in the background.&#x20;

### Start Task node

<figure><img src="/files/xtFU5tQ45inyTIV6S5fQ" alt="" width="61"><figcaption></figcaption></figure>

Use this node to start a task created in the project as a background process. Every process has a unique job ID that can be stored in a text dossier item to be used later.

{% columns %}
{% column width="66.66666666666666%" %}
*Properties*

* (Optional) Store job instance ID: Text dossier item to store the ID.
* (Optional) Task arguments: A list of optional arguments that can be provided as input for the task. The parameters are declared in the input folder under the task itself in the navigation section.

*Exits*

* Task queued: The task has been queued to run anytime now.
* Task queue limit reached: The task has not been queued because the limit has been reached.

{% endcolumn %}

{% column %}

<figure><img src="/files/UawTItFsMOtZtrA7bg3C" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Stop task node

<figure><img src="/files/6DMgQdE9zCZvTSo6c9PW" alt=""><figcaption></figcaption></figure>

Use this node to stop a running task with a specific ID.

{% columns %}
{% column width="66.66666666666666%" %}
*Properties*

* (Required) Job instance ID: Stop running task with this ID.

*Exits*

* Default exit: Task has been successful stopped.
* Error: An error occurred whilst stopping the task.

{% endcolumn %}

{% column %}

<figure><img src="/files/hGLlGm5o41jSAnOIKsT8" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Task status node

<figure><img src="/files/ErIKG03XYpHE4H0cAMu3" alt=""><figcaption></figcaption></figure>

Use this node to retrieve the status of a running task on demand.

{% columns %}
{% column width="66.66666666666666%" %}
*Properties*

* (Required) Job instance ID: The running task instance ID to retrieve the status from.
* Store status: Text dossier item to store general status information.
* Store feedback: Text dossier item to store custom feedback from the running task. For more information see the Task feedback node.
* Store error: Text dossier item to store general error information.

*Exits*

* Task queued: Task has been queued to run later.
* Task running: Task is running.
* Task stopped: Task has been stopped.
* Task stopping: Task is in the process to be stopped.
* Task error: Task has an error.
* Task completed: Task is completed.
* Task not found: Task has not been found.
* Default exit: The exit when other exits are not handled.

{% endcolumn %}

{% column %}

<figure><img src="/files/yz3pZqzHoGBlYZDyxnsW" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Task feedback node

<figure><img src="/files/RNeVxL50sC2NDQhICpPt" alt=""><figcaption></figcaption></figure>

Store any information of this running task instance to be read from other WEM runtime sessions.

{% columns %}
{% column width="66.66666666666666%" %}
*Properties*

* Feedback expressions: The shared information to stored.
* Append feedback: Should the extra information be appended?

{% endcolumn %}

{% column %}

<figure><img src="/files/Z5hpQTq2CIiVux7cEJHM" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

### Task input folder

Is a dossier folder of parameters for the current task. The arguments are given by the Start task node. Note that <mark style="color:red;">**no lists or calculated fields**</mark> can be created as input parameter.

{% hint style="info" %}
You can read a more in depth guide on how to create an ASync task in the Tips and Tricks section: [Create a Async Task](/platform/tutorials/tutorials/create-a-async-task.md)
{% endhint %}


---

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

```
GET https://docs.wem.io/platform/wemmodeler/flowcharts/async-tasks.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.