When a sub-playbook loops, which task tab will allow an analyst to determine what data the sub- playbook used in each iteration of the loop?

When a playbook task, including a sub-playbook, is configured to loop, it executes multiple times. Within the Cortex XSIAM War Room or playbook debugger, an analyst can investigate the details of each execution. By selecting the specific task, the UI provides a dropdown menu to select each iteration of the loop. For each selected iteration, the Inputs tab displays the precise data, arguments, and context keys that were passed into and consumed by that specific run of the sub-playbook. This allows the analyst to trace the data flow for every loop cycle.

A. Input Results: This is not a standard or recognized tab name within the Cortex XSIAM/XSOAR playbook interface. The correct term for the data consumed by a task is "Inputs".
B. Outputs: The "Outputs" tab displays the data and results that were produced by each iteration of the sub-playbook, not the data that was used as input.
C. Results: While a task produces results, "Results" is a generic term. The specific, designated tab for viewing the data consumed by the task is labeled "Inputs".

1. Palo Alto Networks, Cortex XSOAR 8 Administrator's Guide: In the section "Work with Tasks in the War Room," the documentation details how to view task information. It states, "You can view details for each task, such as the task inputs and outputs... For looping tasks, you can see the inputs and outputs for each loop." This confirms that "Inputs" is the correct tab for viewing the data used in each iteration. (Reference: Cortex XSOAR Administrator's Guide, section on War Room task investigation).

2. Palo Alto Networks, Cortex XSIAM Playbook Reference: The playbook development documentation consistently refers to the data a task consumes as "inputs" and the data it produces as "outputs." When debugging a looping task, the UI is designed to show the distinct inputs for each iteration. (Reference: Cortex XSIAM Developer Documentation, section on Playbook Basics and Debugging).