OmniStudioAdvancedintegration-procedureerror-handlingomniscript
Architect Integration Procedure try-catch-finally error propagation to OmniScript UX
Real World Scenario
Health plan enrollment OmniScript shows generic error when eligibility IP fails; members abandon without knowing missing documentation is fixable.
Expected Answer
• IP Try-Catch blocks return structured error JSON code message userAction
• OmniScript Conditional View branches on error code specific messaging
• Finally block logs correlation Id to Integration_Log__c always
• Retry action button re-invokes IP same input idempotent
• Support reference number in error for call center lookup
• Never expose stack trace or API key in user message
• QA test matrix all IP fault paths not only happy path
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. IP Try-Catch blocks return structured error JSON code message userAction. OmniScript Conditional View branches on error code specific messaging. Pick based on your integration pattern and team capability. Generic OmniScript errors drive abandonment—structured IP errors enable self-service recovery. Optimize for scale and operational observability.
Architect Perspective
Generic OmniScript errors drive abandonment—structured IP errors enable self-service recovery.