I had an issue with a solution-based Flow and I cannot figure out why it did what it did.
The solution contains a powerapp and two flows, we'll call them Flow_Start and Flow_Process (child flow).
When a user submits a request from the app, it calls Flow_Start. That sets some variables and then calls Flow_Process. Flow_Process initiates approvals and updates some sharepoint fields.
I had a user submit a single request. Flow_Start ran once. Flow_Process ran 3 times (3 separate runs), sequentially as each was approved.
There was an issue that caused the first two to fail, because there was a blank number field in SP it was trying to add to.
The only step after that is 'Respond to flow'. After the first 2 failures, I set the number field in SP and the last run went through successfully. No additional runs after that.
So somehow, that step failing caused Flow_Process to re-trigger. 'Respond to flow' is just set to run on success, so it was skipped.
Based on that, it seems that if a child flow fails (without appropriate error handling at least), it just restarts?
Hoping someone can confirm the expected behavior here.
Thanks
