Possible Way to Breakpoint in Logic Apps
Take advantage of a setting called Configure Run After to include breakpoints while testing your Azure logic App
Occasionally as you are developing a Logic App you may encounter a situation where you need to change and upstream Action that will change the way data is Outputted. That change could have ramifications downstream.
To prevent certain actions from occurring when you are editing and testing a Logic App you can take advantage of a setting called Configure Run After. This way you can view the outputted data and adjust downstream actions as needed where they call Dynamic Content or Expressions.
To do this use the ... ellipses on the right of the action you do not want to run. This in effect creates a sort of stop \ breakpoint in the flow.
Here you can remove and untick "is successful" and tick "has timed out" click Done
Afterwards you will see the breakpoint line red
Before running the Logic App do not forget to save changes
Now when we run a test we can get the updated output data and the rest of the Logic App will not run
As an added bonus you can use the Configure Run After if errors occur or time outs occur by design and you want to continue running the actions downstream. The configure run after is very helpful and sometimes overlooked when troubleshooting, testing, or just by design because you don't want to fix upstream outputs.
NOTES: