Fixed duplicate key exception for Hangfire jobs with AutomaticRetry #3631
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.
Resolves #3626
@bitsandfoxes I'm not super familiar with the Hangfire integration. Is this sane? My guess is that
OnPerforming
is being called multiple times with the same context because @vrelk-net decorated the job with[Hangfire.AutomaticRetry(Attempts = 5)]
... so all OK on the first attempt but on subsequent attempts aSentryCheckInIdKey
is already on the context (from the first attempt).