It would be good to see some logging i.e. debug statements that could read various data sources/connections and log state information. This should be available in the Flow run logs.
Thank you for the suggestion, this is a good idea. In the meanwhile you can use the Compose action to compose a message that you can see in the output log.
Is this already possible? I'm really surprised this is over a year old and no one at Microsoft has even commented here.
This thread seems to suggest you can see logs, but it is not apparent immediately apparenty where:
The idiot friendly GUI interface is great, but it would be really awesome if there was some way to turn on request/response tracing when you have issues and look at those nitty gritty results.
Especially with the current lack of stability with the GUI. I can't believe how many times in 2-3 days I've already hit that page, "It looks like something went wrong". I'm willing to take on a certain amount of bleeding to use cutting edge stuff like this, but it would be nice if there was the good'ole pure log files to look at when the fancy stuff is failing.
How about making the step completion codes available in dynamic data so they can either be tested (success, failure, duplicate, not found are four very common requirements) or surfaced in the run log using Compose.