I have an Oban Workflow that I want to limit so that only 1 Workflow will run for a user at a time, but not block for other users. From the config it looks like I can do this per worker, but my workflow could have concurrent workers. I don’t know if there is a way to do this with Oban config help…

[image] ryanwinchester: I don’t know if there is a way to do this with Oban config Yes! Indeed, there is. With Pro v1.6 you can set a global partition by workflow_name or some other unique attribute of that users workflow. (That’s really up to you). It’s more about concurrency and not uniquen…

Depending in the users amount, I would use a GenServer per user, saving in the state the jobs queue and a tick function wich take the first in the list, execute and update the state… If you want to persist the state in case of crashes and you are not using a cluster, you can save the state in ETS… …

Nice! Is 1.6 ready for prod use yet? Just reading 1.6 docs now. Can I use the new context in the partition? e.g. global_limit: [allowed: 1, partition: [meta: :workflow_name, context: :user_id]] *edit: looks like no. workflow_name will work, though. thanks

[image] ryanwinchester: *edit: looks like no. worker_name will work, though. thanks Worker name or workflow name? :thinking:

yeah workflow_name :sweat_smile:

We run it in production. It’s in rc for a while, at least a month. Totally up to you.

*edit: looks like no. workflow_name will work, though. thanks Bummer. Is that because Oban doesn’t support partitioning by context keys yet?

[image] lessless: Bummer. Is that because Oban doesn’t support partitioning by context keys yet? The context is stored by itself, it isn’t stored with every job. That means it’s impossible to partition by anything within the context because it’s simply not available on every workflow job.

Elixir Programming Language Forum

Unique Workflows (no overlap per user)

Questions & Help Questions

ryanwinchester April 9, 2025, 3:43pm 3

it’s an Oban Workflow that I am trying to run uniquely