IntegrationIntermediatemulesoftoauthtoken-refresh
Handle MuleSoft Salesforce connector token refresh failures in production
Real World Scenario
Connected app secret rotated; MuleSoft flows fail INVALID_SESSION_ID until manual redeploy causing 4-hour order outage.
Expected Answer
• Named Credential or OAuth module central token refresh
• Automated secret rotation pipeline updates MuleSoft secure properties
• Alert token refresh failure first error not after backlog
• Health check flow validates token every 15 minutes synthetic query
• Runbook secret rotation zero-downtime dual credential period
• JWT bearer eliminates refresh token rotation pain
• Staging validation secret rotation before production
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Never fail silently. Named Credential or OAuth module central token refresh. Implement retry with exponential backoff and a dead-letter queue for permanent failures. Token refresh failure is silent killer—synthetic auth health check every 15 minutes minimum. Balance speed of delivery with maintainability.
Architect Perspective
Token refresh failure is silent killer—synthetic auth health check every 15 minutes minimum.