Azure Logic App (Consumption) is one of the most used integration services for orchestrating critical workflows, and an error in it would largely affect your business continuity.
By default, Logic App allows handling errors using the Configure run after settings at a per action level. For more complex scenarios, it can be done by setting up Scope action and implementing try-catch/try-catch-finally statements.
However, getting a detailed error message can be challenging with just these default features. That’s why we got a whitepaper from industry experts Sandro Pereira and Luis Rigueira to explain alternative approaches.
What’s in store for you?
This whitepaper will give you a detailed understanding of the following:
- An introduction to implementing error handling in Logic Apps
- Guidance to use the result() expression in simple workflows
- Taking the low-code/no-code approach for handling generical errors
- Code first approach: Using an Azure Function
