-
Notifications
You must be signed in to change notification settings - Fork 40
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
Retry from dashboard does not work #122
Comments
Hey @collimarco, sorry for the delay! That sounds like a bug, the job should be retried. Definitely not by design. Would you be able to get some logs of the request to retry to see if that gives us a clue of what's going on? |
@rosa Yes, this is the stack trace:
|
Hey @collimarco thanks a lot for that! I meant the logs for the request to retry that job, that is, the request to:
or similar route in your app. |
@rosa This is the only related POST request that I can see from the logs:
So the request seems successful. I also see a green banner saying that retry has been scheduled successfully when I click the "Retry" button. I also see that the badge on "In progress jobs" tab is incremented by 1... However as soon as I refresh the page, even after 1 second, the job is in "Failed jobs" again (and executions count is not changed). I don't see any other relevant logs |
@collimarco, I think this is a bug in Solid Queue 🤔 I assume you're using that and not resque, right? I'll look into it. |
@rosa Yes, I am using Solid Queue |
We have a Job listed in "Failed jobs" with this error:
It is clearly a temporary network error.
The job has this retry policy:
I also see this status for the retries (in the section "Raw data"):
The problem is that when I click "Retry" in the dashboard it seems that the Job is not even retried and after a few seconds it's immediately sent to "Failed jobs" again.
The executions count is not incremented (does not change) and from the time it takes to execute the Job I am pretty sure that it is not even trying to execute it again.
Is this by design when you reach the max number of attempts? (In this case it would be better to clarify this behavior in the dashboard)
Or is it a bug?
The text was updated successfully, but these errors were encountered: