Change actions that have dependencies


This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

One of the powerful aspects of automated flows is that any action can use data output by any trigger or action above it in the flow; however, this presents a challenge if you want to change a step at the top of the flow on which other actions depend. Previously, the flow designer would block you from making such a change because doing so would break other actions in the flow.

The new Flow checker highlights actions within a flow that need to be repaired. Now, you can delete or rename actions on which other steps depend. Use the Flow checker to fix the issues that arise.