In FortiSOAR 7.6, step utilities are advanced configurations applied to individual playbook steps to control logic, timing, and data processing. According to the Playbook Engine architecture:
Timeout (A): The Timeout utility allows an administrator to define a maximum duration for a step to complete. If the step does not finish within this designated window, the playbook engine terminates the step and the overall playbook execution to prevent hung processes and resource exhaustion.
Loop (B): The Loop utility is used for iterative processing (e.g., performing a lookup for every IP in a list). A playbook step can only contain one Loop utility configuration. If multiple iterations are required across different data sets, they must be handled in separate steps or nested child playbooks.
Condition (D): The Condition utility (Decision Step logic) behaves differently when a Loop is present. If there is no loop, the condition determines if the step executes once. If a loop is present, the condition is evaluated for each item in the loop, effectively acting as a filter for which iterations proceed.
Why other options are incorrect:
Variables (C): The Variables utility (Set Variable) is used to define new custom variables within the scope of that step for later use. It does not " store the output of the step directly in the step itself " ; step outputs are automatically stored in the vars.steps. < step_name > object by the engine regardless of the utility used.
Mock Output (E): The Mock Output utility is used for testing and development to simulate successful data returns without actually executing a connector. It uses JSON format, not HTML, to ensure the simulated data structure matches what the playbook engine expects for downstream Jinja processing.
