Before
Teams likely had to start parent and child dataflow refreshes manually, switch between refresh history views, and repeatedly check whether each operation had completed. They also had to decide when a dependent dataflow could safely be started and repeat the process for subsequent updates.
How it works
- Discover the configured workspaces and dataflows, then start the first refresh on demand or according to schedule.
- Monitor refresh execution and check the parent dataflow status, waiting whenever a dependency is still in progress.
- Start and monitor each subsequent dependent refresh until the configured cascading sequence is complete.
Workflow details
- Trigger and discovery: The workflow starts manually or on a predefined schedule, then retrieves the available workspaces and the dataflows or datasets within the relevant workspace so the configured refresh sequence can be addressed.
- Initial refresh: It starts the first dataflow refresh and captures its execution status, then repeatedly checks that status until the refresh reaches Completed.
- Dependency validation: After the initial refresh, the workflow checks the main or parent dataflow status. If the parent refresh is still in progress, it waits and continues monitoring rather than immediately starting the next dependent update.
- Cascading updates: Once the required status condition is met, it starts the next dataflow refresh, monitors it to completion, and repeats the parent-status check for the configured downstream sequence. The process continues through the linked refreshes defined in the workflow.
What changed
Refreshes now progress through the configured dependency sequence automatically. Status polling and the decision to wait or start the next dataflow occur within the workflow, so people no longer need to coordinate each handoff manually.
Work removed
Manually starting each parent and dependent refresh, reviewing refresh statuses repeatedly, checking whether the parent dataflow has completed, deciding when to launch the next dataflow, and repeating those checks for subsequent updates.
Expected outcome
Each scheduled or manual run can replace at least two recurring refresh-status checks and the associated dependent-refresh handoffs, with downstream updates launched only after the configured completion conditions are met.
