So let me state I am not saying Flow in a flow is the answer, but I am answering you
1. You create a Manual Flow
test it love it save it
2. Create the parent flow, (scheduled, Triggered, manual)
3. Inside you use the Run a Child Flow Action and point to your Step 1 Flow
Thats it... and you can pass data in and use the data from the child flow.
So yes flow in a flow is and has been a thing forever.
As for why your flow is not triggering... There are only a few reason
1. Back end change broke it and MS will fix it hopefully
2. someone changed something in the back end "thing" that is supposed to trigger it so it doesn't trigger and needs to be updated
3. The flow is literally hosed and the meta-data in the back stinks and bleh.
4. Someone turned it off (check in the Details Page to make sure)
5. Bad trigger condition
6. A change has made the custom trigger condition stop it from ever triggering.
Options
1. Remove the Trigger and re-add it, yes you can delete a trigger, and then re-add it. If I am able, I switch it to a manual trigger, unless I need the data from the Trigger in which case I cannot do this as it won't let me save. But either way, remove it. re-add and configure it.
2. Create a copy of your Flow using Save As in the My Flows or shared to me whatever. Test that one, many times bingo this works but sucks as it's a different flow and needs to be deployed to whereever you are using it so that its the correct one
3. Turn it back on
4. Turn it OFF, then back on.
5. Do a Test, go into the Flow, click Test, if its a triggered Flow it will just sit there Spinning until you do the action that should trigger it.
See if that makes it start working again.
6. verify the/ if any custom trigger conditions
etc.
If this helps resolve your question please Mark as such and maybe a like. THanks!
