ECA processing queued task

Available since: 1.0.0

Provided tokens

Token	Description
[event]	The event.
[event:machine_name]	The machine name of the ECA event.
[session_user]	The user account that dispatched the event, regardless if ECA is processing models under a different account. This is only available if ECA is configured to always run under a specific account.

Fires when a queued ECA task is being processed. Tasks are placed in the queue by the 'Enqueue task' action and processed during cron or manually.

The task carries token data set by the action that enqueued it, making those tokens available to subsequent actions and conditions.

Fields

Task name

The task name will be used to identify, what type of task is to be processed. When multiple tasks are created that are of the same nature, they should share the same task name.

The task name used to identify what type of task is being processed. Must match the task name used in the 'Enqueue task' action.

Task value (optional)

An optional additional value for finer-grained filtering. Combined with the task name to determine which ECA model handles the task.

Distribute: Process tasks of this name in their own queue.

When enabled, tasks with this name are processed in a dedicated queue, separate from the default ECA queue. This allows independent processing and cron management.

Cron run time (seconds)

Please note: This option is only available when the Distribute option is enabled above. Leave empty to disable processing when running cron.

Only available when 'distribute' is enabled. Specifies how many seconds the cron worker should spend processing tasks from this queue during each cron run. Leave empty to disable cron-based processing.