1
2
3
4
5
6
7
What if, instead of figuring out locking, we created a unique but consistent schedule id (job `id`) across workers - then because `rq` uses `hmset` for `Job.create` we end up updating the existing key. 

If 30 schedulers all publish the same scheduled job (with the same ID), only one of them persists in redis?

An unset `id` when calling a `Scheduler.schedule` or `Scheduler.cron` causes each invocation to get it's own random and unique `uuid.UUID4`, which I believe is at the heart of the issue.

Let me know if there is a flaw in my logic.