Repository navigation
docs: correct production concurrency and idempotency guidance - #602
Merged
Merged
Conversation
|
ueberBrot
force-pushed
the
docs/production-guidance-rate-limit-spec
branch
from
October 8, 2026 11:56
f477c4b to
4ba481e
Compare
ueberBrot
enabled auto-merge (squash)
October 8, 2026 11:56
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.
Summary
Correct production guidance that could lead operators to confuse concurrency with request rate, assume heartbeats extend absolute locks, or use a duplicate check that races with another Worker.
Evidence
After: Guidance describes the actual Claim recovery behavior and uses stable provider keys or a unique record committed with balance changes in one transaction. Linked Jobs and Workers pages follow the same contracts.
Merge Danger
Door: two-way
The documentation corrections can be reverted.
Blast Radius: documentation
Operators may use these examples in their applications. Provider retention, immutable request details, transaction support, and reconciliation still require application-specific decisions.