Repository navigation
Bound background queue chains to prevent stale deployment spending - #52
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Failed background reconciliation could publish fresh queue messages indefinitely. Vercel pins those messages to the originating deployment, so obsolete releases kept running workers and calling Cantelop after newer releases went live.
Bound each wake-up chain to 60 seconds, coalesce callers into five-second delivery slots, and retain wake-up messages for only one minute. Consumers acknowledge expired, malformed, and legacy wake-ups before loading services; failed deliveries back off and stop after three attempts. Durable work remains in Postgres and the minute cron recovers it.
Validation: all 70 service tests passed against a temporary PostgreSQL database, including five queue regression tests; service TypeScript checking and the production Next.js build passed.