Flow Debugger No Longer Handles Exceptions

Unknown

Flow Debugger No Longer Handles Exceptions

Unknown

I am using version 5.11.0.60922.

In all previous versions, if an exception is thrown in the debugger, you were able to select the offending step and examine inputs. And if you examined outputs, the outputs showed the exception that was thrown.

The current version of the flow debugger does not do the above.

In the current flow debugger, the offending step is highlighted. But it is no longer possible to view the inputs/outputs of the step.

In the following example, I’ve created two simple steps. Step one creates an empty StringList (data type is String[]). Step two uses “Get Item by Index” with a constant to try and retrieve StringList[1].

I expect the flow to raise and exception while in debug; and it does… See here:
[img]https://tirade.decisions.com/decisions/Primary/largefilehandler.ashx?fileReferenceId=2bb3f4c0-6c03-4562-a00a-3db58c014f8a[/img]
But clicking on [i]Execution 1, Execution 2[/i], or [i]Execution 3[/i] does nothing. It is now literally impossible to view the inputs to this step.

Unknown

Hello,

This was a known issue and is confirmed to be fixed in 5.12. Let us know if you have anymore questions.