-
-
Notifications
You must be signed in to change notification settings - Fork 408
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
php artisan queue:retry fails #762
Comments
Can you show the code of the job? |
This should be fixed in 73a4a30. Could you try running |
Fixed in 73a4a30 |
I'm still having the issue in stancl/tenancy version 3.5.0 and Laravel 8.38.0. My config is multi database. I have QueueTenancyBootstrapper and DatabaseTenancyBootstrapper in tenancy.php config. I have forced the database queue driver to use the central connection with
in config/queue.php Note that my job got dispatched from the tenant context. I don't know what else to do. Thanks! |
Can you show the code of the job? |
Sure
|
Hmm, could I see your:
And does the issue happen on |
config/queue.php
config/database.php
.env
The code that dispatches the job is a StateMachine linked to a model property (status). When I transition the status some hooks are triggered. In some controller:
In OrderStatusStateMachine.php
The issue happens only on |
Hmm, that's strange. Could you add some Also, what makes the job fail? |
I can reproduce the issue in 3.4.6, with 3.5.0 fixing it.
|
No worries, appreciate that you tested it! It was a bit half-blind debugging for me as I haven't encountered this myself before partially reproducing it in some tests, so the feedback is helpful. |
Bug description
Hey everyone,
Whenever I have a failed job, calling
php artisan queue:retry all
fails.The error message I am getting is:
Steps to reproduce
Setup an empty Laravel project with this package.
Create a job.
Make sure the job fails.
Try running
php artisan queue:retry all
Expected behavior
Calling
php artisan queue:retry all
should properly retry the job.Laravel version
8.75.0
stancl/tenancy version
3.4.5
The text was updated successfully, but these errors were encountered: