Links

Async Tasks

A collection of nodes to provide Async Task features
The Async Tasks feature is currently being developed for a future Feature Release (3.14) and not yet available.
The Async Tasks feature will only available in the WEM Kubernetes Private Cloud Runtime (not on current Shared Cloud for EUR/APAC zones).
When released, we will be able to add some screenshots and further information if needed.

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.

Start Task node

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

Stop task node

Use this node to stop a running task with a specific ID.
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.

Task status node

Use this node to retrieve the status of a running task on demand.
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.

Task feedback node

Store any information of this running task instance to be read from other WEM runtime sessions.
Properties
  • Feedback expressions: The shared information to stored.
  • Append feedback: Should the extra information be appended?

Task input folder

Is a dossier folder of parameters for the current task. The arguments are given by the Start task node. Note that no lists or calculated fields can be created as input parameter.
Last modified 4mo ago