Capbility to run LogicApp in verbose mode
When user opens the LogicApps designer in the portal, there is a "Run" button to execute the workflow. There could be another useful option to "Run in verbose mode". When user clicks this option, separate OUTPUT window would launch in a new blade. During this mode, runtime information could be captured in the output window along with the time stamps and other useful micro-details. Also, user can write custom debug traces to capture various runtime variables.
[Argument] : Although, this can be achieved using Trigger History and Run history.
[Counter-Argument] : From the developer point of view, during development phase, its painful to perform multiple clicks repetitively and navigate through multiple blades to gather some information of a logic app run. Here, developer simply wanted a single flat image of flow run and capability to know the runtime state of any variable or a parameter.
Alternatively, flat image could be achieved by the providing capability to download the flow run as a flat file.
[Counter-Argument] : But this does not provide the capability to write custom traces. Although, there could be alternative to write tracking information for debugging but that will be a throw away effort when you are done with the development, as you do not want to capture too much information for a production run. Running logic app in verbose mode will capture debug traces but not in its a actual run.
Also, getting detailed information regarding logic apps in verbose mode will help developer to understand the runtime behavior more accurately and will help him build more optimized LogicApps (provided what optimizations are done by the runtime are captured in the verbose mode).