Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get rid of failed jobs when retrying the same job (and this finally had succeed) #134

Open
adantart opened this issue Sep 2, 2023 · 2 comments

Comments

@adantart
Copy link

adantart commented Sep 2, 2023

Maybe I'm using it wrong ...

I have a Job and goes to Laravel's "job" table normally.
(in my testing case I have something to FAIL this job the first 2 times ...)

So it fails... and goes to Laravel's failed_jobs table.
Because the Job retry configuration it goes again to job table.

It runs, it fails again (second time, because I want to do it ;-)
Go to failed_jobs and retry ...

Third time, it's OK !

Everything run perfectly in Laravel.

But in Laravel Queue Monitor UI I see this:

image

and in the queue_monitor table I have this:

image

I have the third attempt success .. but also 2 lines with the button RETRY.

If I hit those buttons, it does nothing ... just refresh the page and then dissapear.

But my question is (and that's because I wonder I'm using it wrong ;-) : how can I get rid of those retryjobs in monitor ?

I mean, they have the same job_uuid, so I guess Monitor knows are part of the same ORIGINAL job.

I don't need them anymore ... the attempts 1 and 2 should not be there if the attempt 3 succeded.

No ?

THNK YOU in advance

@adantart adantart changed the title Get rid of failed jobs when retrying the same job Get rid of failed jobs when retrying the same job (and this finally had succeed) Sep 2, 2023
@romanzipp
Copy link
Owner

I can look into hiding the retry button if a job has been retried. But the queue monitor is more a backlog of job activity rather than a dashboard. And indeed the UUIDs are the same but the numeric IDs provided by Laravel are different so this behavior is expected

@freyca
Copy link

freyca commented Apr 18, 2024

Hi there, not only gets the Failed ones, some of theme get stucked as "queued", although they had failed
stuck_jobs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants