Is it good Idea to set the interval to 0 as a way to force the rest of the workflows to wait for this workflow?

Hi,

Scheduling a workflow on a list includes setting the interval.
The docs contain the following:

  • 0 seconds: setting the interval to 0 is technically possible, but it has the drawback of blocking other scheduled workflows until the entire batch is completed. To avoid this bottleneck and allow for smoother processing of scheduled tasks, it’s often more effective to leave the interval at its default setting. This approach helps in managing the execution flow more efficiently, ensuring that all scheduled workflows are processed without significant delay.

I have a workflow that should be run on a list and there is another workflow that should wait until the entire batch is completed. I can make a loop that triggers the next workflow when it reaches the last iteration, but this is slower than scheduling a workflow on a list. If I scheduled a workflow on a list I will not be able to force the next workflow to wait unless I set the interval to 0 (according to what I understand from the docs).

So is setting the interval to 0 a reliable way to force the next workflow to wait until the workflow finished running on the list?