Provide debugging, exception handling and logging/tracing capabilities
On premise debugging is difficult (from a BizTalk perspective), but in the cloud it is even more difficult. We need to have a way to be able to easily debug workflows to improve productivity.
Tracking, tracing and logging are easy to implement on development, but when an application moves to production it impacts performance heavily. We need to have an out-of-the-box way to enable/disable these features to be able to check workflows on production systems.
So far I haven't found anything about exception handing in the logic apps. What happens when a value from one API is a string and that is used in another expecting an decimal?
We need to have exception handling to gracefully be able to handle exceptions.
We’ve released the first few phases of this so completing the item and can re-open a few more. For tracking you can now subscribe to Azure Diagnostics and get any run data about your Logic App – you can also track any inputs/outputs so you can trace your workflows. Debugging can use diagnostics or the run details blade in Azure. Finally for exception handling in a Logic App you can use the new ‘runAfter’ functionality to say “run After this step failed” – you can also put items in a scope and use the “@result()” to check if any acitons failed in a scope to act accordingly. More work coming, but for now marking this item as complete.
On failed actions in logic apps we cannot send failure messages on outlook. So If we send failure action messages that can be easy to identify the problem.
Marty Walser commented
Related question -- I have a exception action that I have created and want to runAfter any one of a number of actions have succeeded or failed. I.e. -- let's say I have steps 1, 2, 3, and then 4. I want to run the other action if any one of them succeeds.
Currently, if I put more than one action in the runAfter block, it works like an AND clause rather than an OR clause. I am looking for the syntax to make it like an OR.
As an example:
"LogTokenFailure": ["Succeeded" ],
"LogTransformXmlFailure": [ "Succeeded" ]
Using this syntax, both of those actions need to succeed for the action to run. But I actually want it to run if either succeeds (the other will be Skipped if it is working correctly).
When are you expecting to release some kind of error handling in Logic Apps?
Michael Olsson commented
3rd party solutions have always found a solution for this problem. I would like to get information on how to extract input and ouput data for action and triggers for our best of breed solution.