Describe the bug
When a job is released via middleware, such as when using rate limiting or Without Overlapping, the job is marked as successful and a retry is created.
This is a bit odd, as at first glance on the dashboard it looks like the job has been retried lots, not that it's been delayed due to middleware.
To Reproduce
Steps to reproduce the behavior:
Dispatch a rate limited job
See the retries be created for the job
Expected behavior
I expect to be able to see the job was delayed due to middleware. Nothing will have happened in the job so it should have a 'released' status and show up on the top bar in a drop-down of 'middleware delayed' jobs.
Describe the bug When a job is released via middleware, such as when using rate limiting or Without Overlapping, the job is marked as successful and a retry is created.
This is a bit odd, as at first glance on the dashboard it looks like the job has been retried lots, not that it's been delayed due to middleware.
To Reproduce Steps to reproduce the behavior:
Expected behavior I expect to be able to see the job was delayed due to middleware. Nothing will have happened in the job so it should have a 'released' status and show up on the top bar in a drop-down of 'middleware delayed' jobs.
Open to other solutions to simplify the UI