IntegrationIntermediateerror-handlingdlqreliability
Design integration error handling and dead letter queue patterns
Real World Scenario
Failed SAP order integrations logged inconsistently; ops discovers backlog of 400 unprocessed orders after two weeks.
Expected Answer
• Standard error envelope: correlationId, source, target, errorCode, payload reference
• Dead letter queue in middleware or Integration_Log__c custom object
• Alerting when DLQ depth exceeds threshold or age SLA breached
• Manual replay UI for ops with validation before reprocess
• Classify errors: transient retry vs permanent fix required
• Automatic retry max 3 with backoff for transient only
• Weekly integration health report to stakeholders
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Standard error envelope: correlationId, source, target, errorCode, payload reference Also consider: Dead letter queue in middleware or Integration_Log__c custom object In practice: Alerting when DLQ depth exceeds threshold or age SLA breached Balance speed of delivery with maintainability.
Architect Perspective
Integrations without DLQ visibility fail silently—architects mandate observable failure paths.