This document discusses exception management patterns in Logic Apps. It begins with an introduction to Logic Apps and key concepts. It then covers different components for exception management like retry policies, run after actions, scopes, and terminate actions. Various patterns for controlling workflow flow, collating error information, and grouping logical blocks are presented. Hands-on examples are provided to demonstrate collating information using scopes. Key lessons learned include using scopes from the start, having the right retry policy, and planning exception handling from the beginning.

1. Exception management
patterns in Logic Apps

2. Who am I?
Wagner Silveira
Principal Integration Architect
Microsoft MVP - Azure
MCSA – Cloud Platform

3. Agenda
•What is Logic Apps
•Exception management components
•Some patterns
•Lessons learned

5. Logic Apps
• Microsoft Integration Platform as a Service (IPaaS) offering
• Business Processes Orchestration in the Cloud
• Azure factor (pay as you go, pay per usage, scale on demand)
• Cloud and Hybrid Integration
• Multiple Trigger Patterns
• Manual Invocation
• Event Based
• Scheduled
• Extensible

6. Concepts
• Workflows
• Triggers
• Actions
• Connectors
• Flow structures

7. Planning for the unexpected
• Try again
• Plot alternative paths
• Divide and conquer
• Finish execution

8. Exception management components
• Retry policies
• Run after
• Scopes
• Terminate

9. Retry policies
• Retry execution based on status code
‐ 429 | 5xx
• Two modes
‐ Fixed  based on interval and count
‐ None
• Out of the box  20s x 4
• Can be configured from designer

10. Run after
• Define execution order
• Based on name and status
• Define success and failure flows
• Can be configured from designer
• Multiple predecessors possible (from code)

11. Scopes
• Group a series of workflow elements
• Can host any action or flow control
• Simplify exception management

12. Terminate
• Force workflow termination
• Define final workflow status
‐ Succeeded
‐ Cancelled
‐ Failed
 Error Code
 Error Message

13. Hands on time
Exploring the tools

14. Patterns
• Controlling the flow
• Collating error information
• Group logical blocks by scope

15. Controlling the Flow
• Similar to try/catch
• Use scope for try
• Use run after for catch
• Use terminate to
control the result

16. Collating error information
• Filter scope results for errors
• Use information
‐ Propagate error
‐ Notify
‐ Log

17. Group logical blocks by scope
• Identify logical blocks
• Wrap them around scopes
• Allow
‐ Compensation
policies
‐ More
granularity

18. Hands on time
Collating information

19. Lessons learned
• Use scope from start
• Use multiple scopes for more control
• Have the right retry policy
• Do Until can replicate retry

20. Takeaways
• Logic Apps have good tools for exception management
• Latest changes in UI makes it simpler
• Scopes can help you control the flow
• Think about the right retry policies
• Plan it from start

21. Thank you!
@wsilveiranz | wagner.Silveira@theta.co.nz