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 context on what went wrong.
The Invictus Framework includes an Exception Handler component that retrieves the actual error message from an Azure Logic App. It then translates this to a human-readable text.
Component usage
Create a new Logic App that acts as a 'fallback handler'. Wrap the actions of a Logic App in a Scope. When an action inside the scope fails, the Logic App calls the Exception Handler's Resolve HTTP endpoint. The component resolves the inner error message either via the Regex Translator component or an AI Interpreter. The calling Logic App then uses a Terminate action to return this resolved response to the Logic App run history. Logic Apps can reuse the same Exception Handler Logic App.
- Use a HTTP webhook to call the fallback Logic App. If anything fails in the fallback Logic App, you can resubmit this and return the response asynchronously.
- Call the component in a scope block. Use the Terminate action to return the response from the 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.