To debug an integration flow (IFlow) and inspect the message payload at every processing step, the log level must be set to Trace. The Trace level is specifically designed for detailed troubleshooting, capturing the complete message content (including headers, properties, and the body/payload) as it passes through each component of the IFlow. This data is stored temporarily, allowing developers to analyze the message's state and transformations throughout the entire process.

A. Info: The 'Info' log level only records high-level information, such as the start and end of the process and any errors encountered. It does not store the payload at each step.

C. Create a script: While a Groovy script can be used to manually log payloads as attachments, this is a development task and not a standard, configurable log level for debugging the entire flow at runtime.

D. Debug: 'Debug' is not a valid log level option within the SAP Cloud Integration monitoring settings for this purpose. The correct and officially designated term for this level of detail is 'Trace'.

1. SAP Help Portal

SAP Integration Suite: In the section "Setting the Log Level for an Integration Flow

" the documentation explicitly states: "To be able to view the message content at the single process steps

set the log level to Trace." It further explains that trace data is available for a limited time (typically 10 minutes) for analysis. (SAP Help Portal -> SAP Integration Suite -> Operating and Monitoring Integrations in the Cloud Foundry Environment -> Monitoring Message Processing -> Setting the Log Level for an Integration Flow).

2. SAP Help Portal

SAP Integration Suite: The "Message Processing Log" documentation details the information captured at different levels. It confirms that only the 'Trace' level provides access to the "Message Content" tab

which contains the payload at various steps. (SAP Help Portal -> SAP Integration Suite -> Operating and Monitoring Integrations in the Cloud Foundry Environment -> Monitoring Message Processing -> Accessing Message Processing Logs and Attachments).