feat: add exponential backoff retry to MQ consumer on receive errors#775
Merged
feat: add exponential backoff retry to MQ consumer on receive errors#775
Conversation
Previously, any error from subscription.Receive() immediately killed the consumer worker with no recovery. Transient errors like GCP oauth2 token refresh timeouts would take down the entire worker until a manual restart. Add receiveWithRetry() with exponential backoff (200ms -> 5s, max 5 consecutive errors) matching the existing scheduler retry pattern. Transient errors now self-heal; persistent errors still fail after the retry budget. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
alexbouchardd
approved these changes
Mar 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
receiveWithRetry()to the generic MQ consumer with exponential backoff (200ms → 5s cap, max 5 consecutive errors)Receive()errors (e.g. GCP oauth2 token refresh timeouts, network blips) now self-heal instead of killing the workerscheduler.goTest plan
🤖 Generated with Claude Code