IntegrationIntermediatesoapsessionrecovery
Handle SOAP INVALID_SESSION_ID automatic recovery in batch integrations
Real World Scenario
Overnight SOAP batch fails at hour 3 with INVALID_SESSION_ID; 2 hours of processed records not committed due to batch rollback design flaw.
Expected Answer
• Commit checkpoint per batch chunk not single transaction entire run
• Session refresh wrapper around every SOAP call retry once on fault
• Stateful batch cursor resume from last successful record Id
• OAuth token refresh before expiry not reactive on fault only
• Alert batch incomplete state not silent partial success
• Migration REST Bulk API stateless job preferred
• Integration test session expiry injection
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Never fail silently. Commit checkpoint per batch chunk not single transaction entire run. Implement retry with exponential backoff and a dead-letter queue for permanent failures. Long SOAP batches must checkpoint—session expiry mid-batch is when not if. Balance speed of delivery with maintainability.
Architect Perspective
Long SOAP batches must checkpoint—session expiry mid-batch is when not if.