Error handling
Errors happen all the time. A file was not found, a folder does not exist, a UI element is missing – all these events could occur, and they will result in an error. Without further intervention, the flow would stop at the point where the error occurred. All further actions will not be executed. But this is often not what should happen. As a flow designer, we would want to check that error, maybe retry and log specific information, and execute the flow with some other actions until it finishes. This is what error handling is for.
On almost all action parameter dialogs, there is an On error button in the lower-left corner. This, of course, only makes sense if the action does something that could potentially go wrong. A Comment action or a Label does not have such an option.
We will see a lot more complex scenarios, but for this first encounter, we want to look at something simple: deleting a file that is not there. Let’s create a new flow and define...
