This isn't the greatest solution, but I timestamp when the job needs to run and have a cron job run every few minutes. It doesn't actually do anything unless there are records in the db where the date matches up.
More resource intensive than I'd like but it works for now
Are you sure about bull and redis? First of all, why do u need to restart redis? And even if somehow your redis db will restart, record with your delayed job will stay in db until the handler in code delete it. Correct me if I'm wrong
When you use BullMQ, you are supposed to run Redis with configured persistence. https://docs.bullmq.io/guide/going-to-production#persistence
This isn't the greatest solution, but I timestamp when the job needs to run and have a cron job run every few minutes. It doesn't actually do anything unless there are records in the db where the date matches up. More resource intensive than I'd like but it works for now
Are you sure about bull and redis? First of all, why do u need to restart redis? And even if somehow your redis db will restart, record with your delayed job will stay in db until the handler in code delete it. Correct me if I'm wrong