fix(cloudflare): calculate retries not attempts#16834
Merged
AbhiPrasad merged 2 commits intogetsentry:developfrom Jul 8, 2025
Merged
fix(cloudflare): calculate retries not attempts#16834AbhiPrasad merged 2 commits intogetsentry:developfrom
AbhiPrasad merged 2 commits intogetsentry:developfrom
Conversation
The `message.attempts` property starts at 1 so we were calculating the number of attempts not the number of retries. Since attempt 2 is the first retry.
Member
|
There seems to be a linting issue, could you run |
Contributor
Author
|
Ah, yeah of course. 2.1 GB of |
AbhiPrasad
added a commit
that referenced
this pull request
Jul 8, 2025
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #16834 Co-authored-by: AbhiPrasad <[email protected]>
This was referenced Sep 29, 2025
This was referenced Oct 7, 2025
This was referenced Oct 15, 2025
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
3 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.
The
message.attemptsproperty starts at 1 so we were calculating the number of attempts not the number of retries. Attempt 2 is the first retry not attempt 1.Currently the retry count is the same as the number of messages in the batch this way:
Additionally this causes the error rate to be quite nice and I have been assured my code is not THAT bad:
See: https://developers.cloudflare.com/queues/configuration/javascript-apis/