In your flow analytics you will still see your handled errors coming through. As flows grow you sometimes might want to wait implementing a flow straight away as a state machine.Īnyway, I would still like to suggest a base setup as shown below. This then may help you develop a more robust flow but be careful that you don’t over engineer your flows. So for the larger flows where you might develop you flow with state driven switch ( state machine alike ) then you could add a try and switch scope box around the code within each branch of your switch step. You will have an additional try & catch in your code. Taking the Try/ Catch principles from all languages like C# and JavaScript you might want to use a try catch around your main code collecting all failures of your code however you might find that within each method/function. This can make you catch section in your flow fairly complicated when you try to handle all failures within a single catch. Today, in the series of error handling posts I will look at the SharePoint connector’s error messages.Īll of these solutions follow the principle of “something has gone wrong and now deal with it!”. By Pieter Veenstra #BadGateway in Power Automate, #BadRequest in Power Automate, #Conflict error in Microsoft Flow, #Not found in Microsoft Flow, #SharePoint Connector in Flow, #Unauthorized in Flow