A developer is troubleshooting an Integration Procedure with two elements: A Remote Action named FetchCart and a Response Action named ResponseCart…

In the Integration Procedure Preview's Debug Log, the execution of each element is represented by a distinct, expandable JSON node named after that element. To inspect the data being processed by the ResponseCart action, including its input (the "data sent to" it) and its resulting output, the developer must examine the ResponseCart node within the debug log. This node provides the complete execution context for that specific step, showing the state of the entire data JSON at the moment the Response Action is executed.

A. FetchCart: This is the name of a node within the data JSON that likely contains the data to be returned. However, the node in the debug log that shows the execution of the response step is named after the action itself, ResponseCart.

B. Response: "Response" is the name of a top-level pane in the Preview UI that displays the final, trimmed output of the entire Integration Procedure, not a specific node within the step-by-step Debug Log.

C. ResponseCartDebug: This is not a standard name for a node in the data JSON or the debug log. While the log contains debug information, the primary organizational node is named after the action element.

1. Salesforce Help

OmniStudio Integration Procedures

"Debug an Integration Procedure": The documentation illustrates the Preview canvas

which includes the Debug Log. The log shows a tree structure where each action in the procedure (e.g.

SetValues

DataRaptorExtractAction) is a top-level node. To see the input and output for a specific action

you must expand the node corresponding to that action's name. This confirms that to see data related to the ResponseCart action

one must look at the ResponseCart node.

2. Trailhead

OmniStudio Integration Procedures

"Test an Integration Procedure": This module provides visual examples of testing an Integration Procedure. The screenshots of the Preview mode's Debug Log clearly show that each step of the procedure is listed by its element name. For instance

the step for a Response Action named "ResponseAction1" would be found under the "ResponseAction1" node in the log.