Support for reservation and retry of failed jobs
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.1k
- Forks
- 285
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 2
Description
We recently switched to yii2-queue and noticed that failed jobs was removed once it reached max retry count. Sometimes job fails due to bugs in code instead of external resource failure. Removing is misleading as it makes failures unseen from developer. and we will lose message from bugs that is hard to reproduce. Indeed developers are free to implement such things on their own. I think it is so basic and worth being part of yii2-queue, like what Laravel queue does.
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
No files, tests, or entry points are named. Start by reviewing how yii2-queue removes jobs after the maximum retry count and compare the requested reservation and retry behavior with Laravel's queue semantics. Done should preserve failed-job information and provide a defined way to reserve and retry it, but the issue does not specify the exact design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100