We've had the below child Flow that we've been using for 3-4 years without issue in that if the conditional evaluated false, it would continue running the actions after the conditional.
The child flow is part of handful of others that are used to integrate two systems. This child flow is called hundreds of times a day.
Within the past month, on two occasions (the most recent being today), I've had users complaining that records aren't showing up in one the systems.
The culprit is this child Flow holding the parent up because, for whatever reason, it just stalls when the conditional is false instead of running the subsequent actions. There are no actions in the false branch. There doesn't need to be. This has never been a requirement in the hundreds of Flows I've built in the past 6 years.
The first time it happened about a month ago. For the hell of it, I made sure Run After is successful, has timed out, is skipped, has failed were all checked. It started working again and processing the the subsequent actions.
As of 10AM Pacific today, it is back to not working. I can pinpoint the time because everything before then ran successfully; everything after then is sitting in a "running" status.
No clue why it is happening again. No error messages. Just hundreds of runs in "Running" status with no feedback that are hung-up on the conditional when it is false for the past several hours.
There are no more "Run After" I can check. The only other option I can think of is to duplicate the subsequent actions after the condition and move them in to the True and False conditions. That is incredibly dumb and duplicative.
Seems like a Microsoft bug, but no where to report bugs. Only a "Feedback" menu. Reporting bugs and offering Feedback are not the same thing.
