Avoid double sending of an outbox message
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1k
- Forks
- 348
- Avg merge
- 12h 28m
- Merged PRs (30d)
- 91
Description
Is your feature request related to a problem? Please describe.
The outbox implementation triggers the send from two angles: the REST API call to send and the background job that ensures messages are sent even if the front-end doesn't trigger an API call.
It is conceivable that the two methods could trigger a send at the same time and thus send the outbox message twice. (Possibly even with more errors occurring down the line, for example if an attachment is involved)
Strategies discussed so far:
- locking the table
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the REST API send path and the background job that sends outbox messages, then examine how both can process the same message concurrently. Define and test behavior for overlapping sends, including cases with attachments; done means concurrent triggers cannot send one outbox message twice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100