Logic app branches
The standard way to write a logic app is to start with a trigger, then work sequentially down through the logic app in series. This approach can take longer than anticipated because of the amount of time needed for Common Data Service/Dataverse or SQL queries. When you are communicating with on-premises equipment and systems especially, there can be a delay while Azure performs a handshake with the system. This is especially noticeable if this is the first run of the day as subsequent runs cache connections.
As a rule, if your logic can be diverted into separate strands, attempt to write your logic app to operate in parallel. Where you are not referencing data from an entity in other actions, these can be split off to operate in a different path or branch.
In the preceding example, the trigger is when a record is created. Next, we initialize a variable for later use. We have a switch...