OmniStudioIntermediateerror-handlingloggingsupport
Handle OmniScript error handling and observability
Real World Scenario
Customers abandon OmniScript at payment step; support cannot diagnose whether IP payment call or Load DR failed.
Expected Answer
• Integration Procedure Try-Catch blocks with structured error JSON to OmniScript
• OmniScript Display error messages from IP response property not generic text
• Log IP executions to custom object or external log with session Id correlation
• Support view FlexCard showing recent OmniScript session status for logged-in user
• Alert ops on IP failure rate spike threshold
• User option to save progress and contact support with reference number
• Test fault paths in QA not only happy path
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Integration Procedure Try-Catch blocks with structured error JSON to OmniScript Also consider: OmniScript Display error messages from IP response property not generic text In practice: Log IP executions to custom object or external log with session Id correlation Balance speed of delivery with maintainability.
Architect Perspective
OmniScript failures invisible to support without correlation logging—instrument IP exits.