feat: 🎸 replace Queue.add_job with Queue.upsert_job
upsert_job ensures only one waiting job for the same set of parameters. On every call to upsert_job, all the previous waiting jobs for the same set of parameters are canceled, and a new one is created with a new "created_at" date, which means it will be put at the end of the queue. It will help to fight against datasets that are updated very often (eg, every minute): they will be treated only when there are available workers.

It's a quick PR to fix the issue that the queues are increasing faster than the availability of the workers and that most of these jobs will be later skipped. Better to reduce the number of results in the queries (by reducing the number of waiting jobs).
feat: 🎸 replace Queue.add_job with Queue.upsert_job: upsert_job ensures only one waiting job for the same set of parameters. On every call to upsert_job, all the previous waiting jobs for the same set of parameters are canceled, and a new one is created with a new "created_at" date, which means it will be put at the end of the queue. It will help to fight against datasets that are updated very often (eg, every minute): they will be treated only when there are available workers.

It's a quick PR to fix the issue that the queues are increasing faster than the availability of the workers and that most of these jobs will be later skipped. Better to reduce the number of results in the queries (by reducing the number of waiting jobs).