Hi @onurbolaca, it can make sense. The execution of your parent workflow would only continue once the last node of your sub-workflow has been executed, so if you want to add an intentional waiting time this could be useful.
It does however take away a bit of visibility as the parent wouldn’t see which node exactly is currently running in the sub-workflow. So unless there are any memory limits at play here I’d try adding the wait to the loop in your parent workflow instead.