SALESFORCE-MEDIA-CLOUD practice question 6 of 15

Users receive an "Apex CPU limit exceeded" error when running the Advertising Sales Management (ASM) flow OmniScript in a Salesforce Experience site. The OmniScript includes an Integration Procedure that contains multiple Data Raptors. In which two areas within OmniStudio should a Consultant check to troubleshoot this issue? Choose 2 answers

Full set: 60 questions
Answer options
A: Action Debugger Correct answer
B: OmniScript Debugger
C: OmniStudio Logs
D: DataRaptor Configuration Correct answer
Correct Answer:
A. Action Debugger; D. DataRaptor Configuration
Explanation

When encountering an "Apex CPU limit exceeded" error in an OmniScript utilizing Integration Procedures and DataRaptors, the issue typically stems from inefficient data processing. The Action Debugger (available in the Preview tab) is essential for tracing the execution time of individual actions to identify the specific bottleneck. Once identified, the Consultant must review the DataRaptor Configuration to optimize queries, remove unindexed fields, or simplify complex formulas that are consuming excessive CPU cycles.

Why Incorrect

B. OmniScript Debugger: While debugging is necessary, the "Action Debugger" is the specific OmniStudio tool/panel used to inspect the request/response and execution times of actions like IPs.
C. OmniStudio Logs: There is no standard "OmniStudio Logs" tool; developers typically use standard Salesforce Debug Logs for backend Apex troubleshooting.

References

Salesforce Official Documentation: OmniStudio -> "Troubleshoot OmniScripts Using the Action Debugger" (Help Article).

Salesforce Official Documentation: OmniStudio -> "DataRaptor Best Practices" -> "Optimize DataRaptor Performance" (Help Article).

Scroll to Top