Book Image

Enterprise Integration with Azure Logic Apps

By : Matthew Bennett
Book Image

Enterprise Integration with Azure Logic Apps

By: Matthew Bennett

Overview of this book

Logic Apps are a visual flowchart-like representation of common programming actions, and are a flexible way to create logic without writing a single line of code. Enterprise Integration with Azure Logic Apps is a comprehensive introduction for anyone new to Logic Apps which will boost your learning skills and allow you to create rich, complex, structured, and reusable logic with instant results. You'll begin by discovering how to navigate the Azure portal and understand how your objects can be zoned to a specific environment by using resource groups. Complete with hands-on tutorials, projects, and self-assessment questions, this easy-to-follow guide will teach you the benefits and foundations of Logic App logic design. As you advance, you'll find out how to manage your Azure environment in relation to Logic Apps and how to create elegant and reliable Logic Apps. With useful and practical explanations of how to get the most out of Logic App actions and triggers, you'll be able to ensure that your Logic Apps work efficiently and provide seamless integration for real-world scenarios without having to write code. By the end of this Logic Apps book, you'll be able to create complex and powerful Logic Apps within minutes, integrating large amounts of data on demand, enhancing your systems, and linking applications to improve user experience.
Table of Contents (17 chapters)
1
Section 1: Logic App Fundamentals
7
Section 2: Logic App Design
13
Section 3: Logic App Maintenance and Management

Default tries on an action

Any logic app action that calls for data will have a retry policy that explains the behavior of the action when a success message is not returned, along with the expected data. Logic app calls to the Dataverse (Common Data Service), SQL queries, or API calls all operate using web technologies, so standard HTTP error codes are anticipated. Codes such as a 408, 429, or 500 error will trigger the logic app to try again and repeat the request, should the Retry Policy option be set to require this:

Figure 9.8 – Retry Policy is set to Default

A 408 error is a request timeout. The logic app has waited for a long period (typically, 2 minutes) and has expected to hear an answer by this point, so it is now requesting that the connection be closed.

A 429 error is a rate-limiting error – there have been too many requests to this resource at this point, so no further requests will be accepted until traffic has been reduced. Sending...