Trigger and Run History

View all triggers to Logic App along with details about inputs and outputs of each trigger and the error reason in case of failure. If there are multiple triggers, the trigger history can be filtered by the trigger, to get the corresponding trigger histories.
It is possible to drill down to every run action to understand the work flow execution. Say for example consider a Logic App with a trigger 'when a new message arrives in the Service Bus Queue'. The requirement is to identify which Service Bus message has been processed in a specific trigger or run action. The message Id of the processed message can be tracked in the trigger or run action detail. Below is an illustration of the same

Read more on how this capability can help in real time debugging at