Hey guys, y'all were pretty helpful with a deeper concept I was trying to wrap my head around, so it's time for a softball (because I'm pretty sure the issue is located between the keyboard and the computer chair).
I've been trying to implement "On Block Error" blocks that will catch any errors thrown by the actions they are encapsulating and handle them so the main flow doesn't fail. Every attempt at this however has failed to catch any errors thrown by the actions the block encapsulates, this is both when I just have actions as well as when I have calls to sub flows that are contained within an "On block error" action.
To help visualize my issue (see pictures below) I created a very basic "example" flow that creates an array of a certain length and, inside of an "On block error" action, it will attempt to assign a a value to an index that is out of bounds for the array (and should therefore throw an IndexOutOfBoundsException upon attempting that action).
I have not set individual error handling actions (namely because "Set varaible" does not have any "on error" properties), but this is applicable to actions that also have individual error handling properties. Every time the flow attempts the action it will cause the whole flow to fail with a runtime error of the index being invalid. The "On Block Error" is not set to throw an error in response to catching one, so the error causing the flow to fail (from my observations) is the one thrown by the action inside of the "On block error" block. It is worth noting that I in the example I am calling this sub-flow from the Main flow, which has the sub-flow call encapsulated in another "On block error" action, which means two different "On block error" actions have failed to catch and handle this error.
I have tried setting it to "Continue flow run" and either "go to the end of block", "run sub-flow", "go to beginning of block", etc. None of these actions take place, it simply behaves as if it didn't catch the error and the error made its way unhandled to the main flow runtime level and caused the flow to fail.
I'm hoping this is just a simple configuration issue but if there are limitations to the "On block error" action that I am not aware of then I will happily expand on other scenarios where I am implementing this action (because none of my attempts with "On block error" have been successful thus far).
Error thrown from the previous run at the bottom reports that the flow was stopped because of the action performed
"On Error Block" configuration
