motivation
Most who have worked with Logic Apps is familiar with the error An action failed. No dependent actions succeeded. This is a generic error that offers no clear information on what went wrong.
Invictus provides an Exception Handler Framework component that retrieves the actual error message from an Azure Logic App and optionally translate this to a human readable text.
Component usage
To centralize exception handling, create a Logic App that acts as a 'fallback handler'. This Logic App calls the Exception Handler component and returns the response. All the other Logic Apps can call this fallback Logic App.
tip
- Use a HTTP webhook to call the fallback Logic App so that if anything fails in the fallback Logic App, you can resubmit this and return the response asynchronously.
- Interact with the component in a scope block and use the Terminate action to return the response from the Exception Handler component to the Logic App dashboard.
Related Bicep template parameters
Use arrow keys to navigate rows. Press Enter or Space to expand a row with sub-properties. Press / to focus the search field.
Press / to filter