Why does using "Pause Flow" in an async flow create multiple background jobs/threads?

RichterBell

I'm working with asynchronous flows in Decisions and noticed that when I use the "Pause Flow" step, it starts spinning up multiple background jobs or threads, even though I expect only one. Eventually, it drops down to a single thread, but initially, there are more jobs than I anticipated. Is this expected behavior, and how can I prevent multiple jobs from being created when I just want a simple delay in my flow?

MalikB_Decisions

Hello,

Yes, this is expected behavior. The "Pause Flow" step is designed to pause and resume flows asynchronously, which can result in multiple background jobs or threads being created temporarily. If you only need a simple delay (not a true pause/resume), use the "Delay Next Step" step instead. This will prevent multiple jobs from being created.

Hope this helps!