Logic App Finding: Multiple run-after configurations when joining parallel branches

Here is my finding of the day: When working with parallel branches, after the execution paths have been joined again, the next action step can have different run-after configurations for each of the previously joined parallel branches! This ability is hidden behind some bad UI/UX, so I discovered it just today and rather “accidentially”. This might not be needed very often, but when, it can help to keep the LA execution paths simpler, since no bulky if-else branching and redundant actions would be needed.

Click on the previous action first, in order to configure individual state constraints in the run-after settings

Since Logic Apps and Power Automate (aka Flow) practically share the same platform fundament, differen run-after configurations can also be created in Flows.

Quick feature comparison of Flows and classical D365 Workflows & what to expect

Finally, I found a comparison chart which outlines dis-/abilities of Power Automate (aka Flows) and the classical Dynamics 365 Workflows. Of special interest for me are pre-images of events and transactions. Looking forward…

Source: Thanks to @prokytom (Tweet)