Closed niconoe closed 1 year ago
Update: apparently, this obscure error disappear after restarting the rq worker. This should probably be done on each deployment anyway. Will fix the deployment scripts!
Deployment scripts updated, it appears to work fine.
I'll double-check in a couple of days, just to be sure the problem is 100% fixed!
Works fine in production.
This happens on both dev and production server, but cannot replicate on my dev machine yet.
The worker queue starts normally, then the following exception happens: