Table of contents
- Introduction
- Moving Tasks from the waiting status
Introduction
When the success or failure of a task depends on another system that processes it asynchronously, the final status of the task is not yet known when the Alumio Route completes. Since the data may not have been fully processed, marking the task as finished or failed immediately can be misleading.
In these cases, it can be useful to set tasks to the “Waiting” status instead. This status can later be updated to Finished or Failed, either through the Alumio API or via the Alumio Dashboard.
Tasks can be set to the waiting status by enabling the “Enable waiting status” checkbox in the Route.
Moving Tasks from the waiting status
As mentioned before, tasks can be moved from the “Waiting” status to finished or failed through the API, and through the dashboard.
Setting Tasks to finished/failed through the API
The asynchronous system that handles the task can use the following endpoint to update the status of the related task:
https://apidocs.alumio.com/#tag/Tasks/operation/updateWaitingTasks
Passing along Task information
To ensure the external system knows which task it needs to update, the task identifier can be added to the data. This can be done with a Value setter Transformer, referencing the task identifier with the following string: @{scope.task}
Setting Tasks to finished/failed through the dashboard
When a task needs to be manually moved from the waiting status, it can also be done through the Dashboard, rather than through the API. There are actions available in the table row and on the task detail page to accomplish this:
