IntegrationIntermediatemaintenanceresiliencedegradation
Handle Salesforce API maintenance windows with graceful integration degradation
Real World Scenario
Salesforce instance maintenance returns 503; integrations retry aggressively extending outage impact to warehouse.
Expected Answer
• Subscribe trust.salesforce.com maintenance calendar programmatically
• Maintenance mode flag pauses non-critical jobs pre-window
• Exponential backoff on 503 honoring Retry-After header
• Read-only cached responses for non-critical lookups during outage
• Queue writes locally middleware replay post-maintenance
• User communication degraded mode banner Experience Cloud
• Post-maintenance reconciliation catch-up job prioritized
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Subscribe trust.salesforce.com maintenance calendar programmatically Also consider: Maintenance mode flag pauses non-critical jobs pre-window In practice: Exponential backoff on 503 honoring Retry-After header Balance speed of delivery with maintainability.
Architect Perspective
Maintenance is predictable—pause retry storms and queue writes instead of amplifying failure.