Forum Discussion
DataflowsError
Hi ArvindJha,
What you're running into is a common behavior in Power Automate, actions placed after each other don't automatically wait for the previous ones to complete unless explicitly configured to do so.
Even if you're using if/else conditions, if both branches or steps aren’t nested properly or controlled with "Configure Run After", Power Automate may still attempt to run them in parallel, especially if the actions don’t have a true dependency link.
Best Regards,
Hammad.
Community Support Team
Thanks for the response but i dont find a way for dependency , transformation runs when extraction is successful but final dataset starts running in parallel
Power Automate doesn’t provide native dependency handling like a full orchestration tool, which makes this little tricky when you are chaining multiple dependent steps.
To enforce a true dependency, especially where the final dataset refresh must wait for the transformation to complete, you’ll need to explicitly check the status of the transformation dataflow before triggering the dataset refresh.
You can try it practically by these few steps:
* After triggering the transformation dataflow, use a loop with “Get dataflow refresh status”.
* Now inside the loop, check if the status is "Completed".
* Only after confirming completion, proceed to trigger the dataset refresh.
This polling approach ensures the dataset won’t refresh until the transformation is actually finished, even if Power Automate tries to run the steps in parallel.
Best Regards,
Hammad.
Thanks for the response , i already have a get dataflow refresh status which triggers transformation when extraction is complete and not allowing another trigger
Since Power Automate allows only one trigger per flow and you've already built logic to check extraction completion before starting transformation, the next step is to ensure the dataset refresh is placed after the transformation status check, not as a separate branch or parallel step.
Here make sure the dataset refresh action is inside the same success path that runs after the transformation dataflow completes. And if you're using a "Do until" or status-check loop for the transformation, the dataset refresh should be outside the loop but placed immediately after it, not in a separate condition block or parallel branch.
This way, the dataset refresh won’t start until the transformation is truly done even if there's no second trigger.
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you,
Hammad.