The "APEX CPU limit Exceeded" error indicates a server-side performance issue where the transaction is consuming too much processing time. The Action Debugger within the Integration Procedure's Preview is the primary tool for diagnosing such problems. It provides a detailed performance breakdown, showing the execution time in milliseconds for each step, including the calls to the DataRaptors. This allows the developer to pinpoint exactly which action is the bottleneck. Once the slow DataRaptor is identified, its DataRaptor configuration must be examined and optimized. This involves refining SOQL queries, reducing the number of fields retrieved, and simplifying formulas to decrease CPU usage.

A. Script configuration: This is too general. The error originates from the server-side Integration Procedure and DataRaptors, making their specific debugging tools more direct and effective.

B. Community logs: There is no specific logging tool named "Community logs" for this purpose. While general Apex debug logs exist, the Action Debugger is the specialized OmniStudio tool for this scenario.

1. Salesforce OmniStudio Documentation: Debug an Integration Procedure. The documentation explicitly details the use of the Action Debugger. It states

"The Action Debugger shows the data that is sent and received from each action in your Integration Procedure... and performance information

such as the execution time in milliseconds." This directly supports using the Action Debugger to identify performance bottlenecks.

2. Salesforce OmniStudio Documentation: DataRaptor Best Practices. This guide provides key recommendations for performance

such as

"To improve performance

select only the fields you need in a DataRaptor Extract." This confirms that reviewing and optimizing the DataRaptor configuration is a critical step in resolving CPU limit errors.

3. Trailhead by Salesforce: OmniStudio Integration Procedures

Unit: Test an Integration Procedure. This module illustrates how to use the Preview tab to test and debug. It highlights that the Action Debugger shows "the time the action took to run in milliseconds

" which is essential for troubleshooting performance issues like CPU timeouts.