No worries, seems like you're getting what we're doing, which I appreciate! 🙂
The goal of our parent flow, in this case, is an attempt to cut down on having to schedule a ton of individual flows with complex dependencies. At my previous workplaces I've always ended up rolling my own flow dependency handlers that would have rules such as "don't build the marts unless all the integrations have reported success, UNLESS it's > 9 am, then run it anyway" and other rules that just keep getting more complex.
Having a single main flow is my attempt at returning to some sort of simplicity, where we only have to schedule a single orchestrator flow and we let it handle first loading integrations, then testing the raw data, then loading the marts, then testing the marts before finally loading power bi (and other exports). I should probably take a screenshot of what it looks like, give me a minute. I don't know if I'll be able to keep it this simple as we add more integrations, but so far it's been working pretty well.