startExecution

Internal. Run-time inputs for the actions of this execution, keyed by action type. An action reads the entry for its own type and treats it as replacing the matching configured values; an action whose type has no entry runs entirely from its configuration.

Only the workflows service may set this field, on behalf of the person running a semi-automated flow task: it forwards what that person chose after checking their permission to run the task. A request carrying action_inputs under any other token is refused with 403 and nothing is stored.

This is deliberately NOT stored on actions[].config. Retrying a step refreshes that action's config from the live flow (see startAction), which would silently drop an override and re-run the action with the configured values — sending the wrong email, or cancelling a flow under the wrong reason. Keeping the inputs on the execution row means a retry replays what the person actually chose.

Internal. Run-time inputs for the actions of this execution, keyed by action type. An action reads the entry for its own type and treats it as replacing the matching configured values; an action whose type has no entry runs entirely from its configuration.

Only the workflows service may set this field, on behalf of the person running a semi-automated flow task: it forwards what that person chose after checking their permission to run the task. A request carrying action_inputs under any other token is refused with 403 and nothing is stored.

This is deliberately NOT stored on actions[].config. Retrying a step refreshes that action's config from the live flow (see startAction), which would silently drop an override and re-run the action with the configured values — sending the wrong email, or cancelling a flow under the wrong reason. Keeping the inputs on the execution row means a retry replays what the person actually chose.

Correlation stamped when the triggering submission entity carried workflow wait claims from a journey link. Consumed by svc-workflows to resume a task waiting on this journey submission.

Loop scope definitions propagated from the flow onto the execution record. Each loop has an id and a source_path resolved against the trigger entity at execution time. Actions referencing a loop's id via their loop_id property run once per item in the resolved array.