Right now this is the biggest limitation preventing me from leveraging MS Flow with clients.
Microsoft Flow currently flows in a single direction (downstream) which makes it really tough to design and implement approval-driven workflows. Without state-machines, it's really not possible to "reject to a specific step" and automate a system that accounts for the real world back and forth nature of workflows.
I've considered doing this with multiple flows that conditionally change-states (by starting another workflow), but it's quite cumbersome to assemble and pass meta-data between them.
I'd love if we had a "jump to step" action that could be called based on a condition.