Hello,
the purge procedure does not delete anything, checking in the database I noticed that in my table the queued_at field is always empty.
I configured my job with the IsMonitored trait as written in the README, looking in the code I saw that my job is inserted into the queue monitor at this point:
|
$monitor = $model::query()->updateOrCreate([ |
In this updateOrCreate the queued_at is not set, my model is created at this time, so the queued_at remains empty.
And the purge command relies on this date to delete, so nothing is ever deleted.
Am I doing something wrong in the configuration or do I need to correct the code to insert the queued_at also in this point?
Thanks!
Hello,
the purge procedure does not delete anything, checking in the database I noticed that in my table the queued_at field is always empty.
I configured my job with the IsMonitored trait as written in the README, looking in the code I saw that my job is inserted into the queue monitor at this point:
Laravel-Queue-Monitor/src/Services/QueueMonitor.php
Line 209 in 9acafc2
In this updateOrCreate the queued_at is not set, my model is created at this time, so the queued_at remains empty.
And the purge command relies on this date to delete, so nothing is ever deleted.
Am I doing something wrong in the configuration or do I need to correct the code to insert the queued_at also in this point?
Thanks!