Why does using "Pause Flow" in an async flow create multiple background jobs/threads?
in Flows
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?
0