Infinite loading on Batches list #1259
Comments
|
Hey there, Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to open up a new issue with a link to the original one and we'll gladly help you out. Thanks! |
|
Hi @driesvints After investigating the issue myself, it seems that the problem arises from the use of the "SerializesModels" trait in the Job class. Specifically, if the serialized model no longer exists, it causes the batch list on Horizon to break. However, you can close the issue if you think it's appropriate. |
|
Hi @LonnyX, thanks for that. I'll reopen this but would appreciate community help to get this fixed. |
|
Thank you for reporting this issue! As Laravel is an open source project, we rely on the community to help us diagnose and fix issues as it is not possible to research and fix every issue reported to us via GitHub. If possible, please make a pull request fixing the issue you have described, along with corresponding tests. All pull requests are promptly reviewed by the Laravel team. Thank you! |
As described on this issue: laravel/horizon#1259 If a model is deleted while it still exists on the batches list (serialized), it will cause the batches list to be broken. The reason for this is that when the unserialize function is called, it tries to invoke the __unserialize() or __wakeup() methods automatically, and if the model does not exist, an exception is thrown.
As described on this issue: laravel/horizon#1259 If a model is deleted while it still exists on the batches list (serialized), it will cause the batches list to be broken. The reason for this is that when the unserialize function is called, it tries to invoke the __unserialize() or __wakeup() methods automatically, and if the model does not exist, an exception is thrown.
As described on this issue: laravel/horizon#1259 If a model is deleted while it still exists on the batches list (serialized), it will cause the batches list to be broken. The reason for this is that when the unserialize function is called, it tries to invoke the __unserialize() or __wakeup() methods automatically, and if the model does not exist, an exception is thrown.
As described on this issue: laravel/horizon#1259 If a model is deleted while it still exists on the batches list (serialized), it will cause the batches list to be broken. The reason for this is that when the unserialize function is called, it tries to invoke the __unserialize() or __wakeup() methods automatically, and if the model does not exist, an exception is thrown.
|
Thanks for sending in a PR! |
Description:
I'm experiencing an issue with Laravel Horizon where the Batches list has an infinite loading spinner (with 404 Not found status on console). The rest of the application seems to be working fine, but I can't access the Batches list to manage my batch jobs.
To resolve this issue, I've had to manually cleanup the _jobs_batches table in my Postgresql 14 database. After doing so, the Batches list is accessible again. But once some batches are dispatched, it happen again
There is nothing on the logs
Steps To Reproduce:
Not sure why or how this happen
The text was updated successfully, but these errors were encountered: