Lost submissions on client side: POST /api/submissions/ is not idempotent
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 176
- Forks
- 74
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 21
Description
Problem
Whenever a client loses the response of POST /api/submissions/ (network timeout, intermittent 5xx, browser/SDK auto-retry), it replays the request.
Every replay creates a brand new Submission row and triggers another Celery run. From the user's side the "initial" submission is invisible (its id was
never returned); from the platform's side we see ghost duplicates that burn quota and worker capacity.
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 at the POST /api/submissions/ entry point and trace how a request creates a Submission row and triggers its Celery run. Clarify the idempotency-key or request identity expected for retries; done means replaying a timed-out request does not create another row or trigger another run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100