Skip to main content
A task is one unit of work inside a route. Tasks are created by the incoming configuration: for each item the incoming returns, Alumio creates one task. The outgoing configuration later picks up these tasks and sends their data to the destination system. Each task stores the entity data, which is the data that was returned by the incoming after the incoming and route transformers have run.

​
Task Status Lifecycle

A task moves through a series of statuses during its life. New The task has just been created by the incoming and is waiting to be picked up by the outgoing. Processing The outgoing has picked up the task and is currently running its transformers and sending the data. Finished The task has been processed successfully. The data was sent to the destination system without errors. Failed An error occurred during processing, for example a 500 error from the destination API. If Enable task retrying is enabled on the route, Alumio retries the outgoing part of the route on this task. Skipped A filter on the outgoing matched, so the data was not sent to the destination system. The task is kept for visibility but is considered done. See Filters on the Outgoing. Waiting The task has been processed but is awaiting manual confirmation. This status only appears when Enable waiting status is enabled on the route. A task in Waiting stays there until it is manually moved to Finished or Failed.

​
Viewing and Managing Tasks

Tasks are visible from the route, incoming, and outgoing detail pages, as well as from the dedicated tasks views in the Alumio dashboard. From there you can:
  • Inspect the entity data of a task.
  • See the logs for a task, including any error messages.
  • Retry a failed task or manually move a Waiting task to a final status.