feat: Unique wallet transaction job for threshold top-ups #3710
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.
Context
Threshold-based wallet top-ups can sometimes enqueue duplicate jobs if the job is triggered multiple times within a short time window. This leads to unnecessary or duplicate credit grants.
To prevent this, we want to ensure that these jobs are uniquely enqueued based on relevant identifiers:
organization_id
,wallet_id
,paid_credits
, andgranted_credits
.Description
This PR adds job uniqueness handling to
WalletTransactions::CreateJob
usingsidekiq-unique-jobs
, but only when theunique_transaction
flag is set to true.unique_transaction
This keeps behaviour backward-compatible for other use cases of
CreateJob
, while enforcing uniqueness where it matters.