Right. That’s the goal.
I hadn’t considered that use case. It would certainly be possible: eliminate the transaction lock and remove the unique period while scheduling.
You could kind of hack it with the current implementation by overriding the unique period within your job so that it’s very short:
use Oban.Job, queue: "scheduled", unique: [period: 1]
If the nodes start at different times that would work, but it wouldn’t be very reliable.
I’ll think about this use case a bit.
