Tasks
A task is a unit of work that occurs every time a Recipe performs an action that requires compute resources. Every time a Recipe invokes an action provided by a connector counts as one task. This includes actions done with all connectors, including AppConnect utilities (eg. Lookup tables, Variables by Workato).
A Recipe job may consist of multiple tasks. The number of tasks executed in a job depends on the data of the specific trigger event and the Recipe logic.
Task rules
In general, all successfully run actions in a job are counted as tasks and failed actions are not counted.
All successfully run actions in ‘called’ Recipe will be counted
All successfully run actions via jobs rerun (e.g. UI, API, Recipe ops) are counted
Successfully run actions in a failed job are counted i.e. if job fails at step 5, step 1-4 are counted
Task counting
Steps in a Recipe with all the following apps are counted as tasks:
Platform connectors
Custom connectors (Installed from the Community Library/customer-built)
AppConnect utilities (JSON parser, Variables, Lookup tables etc.)
The following table shows a breakdown of how tasks are counted with the different Recipe steps:
Action | Count |
|---|---|
Trigger | Will not be counted as a Task |
Trigger conditions | Will not be counted as a Task |
Search/Create/Update/Get/Upsert/Lookup etc. | Task is incremented by 1 for each of these Actions |
Actions in repeat (for each loop) | The Task is incremented by 1 for every action in the loop. |
Control statement (If, Error monitor, stop) | Will not be counted as a Task |
Batch/bulk operations | Task is incremented by 1 |
Callable Recipes
If a Recipe is called successfully, the call to the Recipe will be counted as a Task. Thereafter, in the child job created, the actions in the Recipe called will be counted as tasks.
Rerunning jobs
All tasks done in rerun jobs are counted as tasks.
Examples
The examples for how tasks may be counted in Recipes are as follows:
Example
Total Tasks per job = 3 (Step 1 + Step 2 + Step 3)