Oban Multiple jobs - what are the best practices to handle something like a workflow using Oban?

Hello everyone,

I was wondering what are the best practices to handle something like a workflow using Oban. From reading the Oban.Pro.Workflow it seems a little bit overkill for my usage.

The current idea:
JobA Succeeds → JobB Succeeds → JobC Succeeds

In the JobB there’s some external http calls to handle data from outside the application.

Currently my ideia is to add a function call at the end of each Job to create and insert in the Oban queue. Is this a good approach?

1 Like

That’s perfectly fine to do so

2 Likes

That’s exactly how you do it.

2 Likes

Alright, thanks for your answers guys.