ISC Workflows fails to fail correctly in a loop

Hi all, :slight_smile:

Bug short description: If the loop childflow ends in an error, the workflow test output will not show the steps it went through.

Bug long description:

See screenshot of workflow tests. In both tests I offer the same input. the HTTP Request points to an API of ISC. In both tests the input results in a 404 message on both iterations of the loop (both tests have 2 iterations).

The only difference between the two tests is whether I end successfully or end in a failure on a 404 not found error. In the first screenshot I fail, notice our the loopOutput is barely useful (I believe this error is actually the error of a bug in workflows, rather then an error on calling the HTTP request).
Notice that the loopOutput on the second workflow is much more clear. You can see which actions and operators it has performed along the way ( although you still don’t see the very last step)


This bug is making it more difficult to test workflows. Regardless of if the childworkflow was successfull or not, it should provide the proper output.

Kind regards,
Angelo

1 Like

Hello angelo,

Yes, it is a bit annoying if you are trying to do some testing. If you want to debug a little bit what i am always doing is going outside the workflow and extract the csv with all the steps that is performing, it is also showing more information than in the test page.

Hope it helps,
Pablo

Hi @pablonovoa, thank you for your response,

I know the alternatives of using CSV and that SailPoint is in addition thinking of showing other details in the UI as well that prevents us from needing to go to the CSV. However, in the end, I would still like SailPoint to fix this bug as it is currently hindering us to perform tests in the UI as designed.

Kind regards,
Angelo

2 Likes

Update from SailPoint Support:

It is accepted as a bug now. Sailpoint Support expects an update today form the engineering team, otherwise they will escalate.