So I have narrowed down the issue
We run multiple instances of our application; a few instances have the queues configured to run on them, and a few instances don’t, but we still start up Oban in the application with queues: []
When the job is inserted by a non Oban Worker there is no partition_key, but if I insert a job via the Oban Worker(one with queues) there is a partition key
That’s strange. That’s a common setup and it is designed to check for partition information on other node types.
Will you please share the result of Oban.config() on the web and worker node? You can omit all the plugins and all of the queue information aside from the partitioned one causing trouble.
Unfortunately I had to get production going so I went with the upgrade and it has things working again.
I can reproduce this locally though where I start up an iex shell without my OBAN_WORKER flag enabled, and no other instances running, and trying to insert a job into a partitioned queue yields no partition_key, would the config of this instance still help?
That’s no problem. The upgrade ensures that jobs without a partition key are processed, it won’t change whether the key is assigned.
Absolutely. If you can reproduce it locally, then the config is helpful.