# ISC Workflows fails to fail correctly in a loop **URL:** \ **Category:** Bugs\ **Tags:** fixed, workflows, sailpoint-identity-security\ **Created:** [November 4, 2024, 4:18pm UTC](https://developer.sailpoint.com/discuss/t/isc-workflows-fails-to-fail-correctly-in-a-loop/88609 "2024-11-04T16:18:51Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [November 4, 2024, 4:18pm UTC](https://developer.sailpoint.com/discuss/t/isc-workflows-fails-to-fail-correctly-in-a-loop/88609/1 "2024-11-04T16:18:51Z")
Hi all, 🙂 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) ![image](https://global.discourse-cdn.com/sailpoint/original/3X/b/f/bfc5e8890ee0a4649184bc83a36da34f2eaef086.png) ![image](https://global.discourse-cdn.com/sailpoint/original/3X/4/c/4cac9a42ea80877d9116abca3341f08c405a8919.png) 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 ---
**Author:** ![pablonovoa](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/pablonovoa/32/18573_2.png) [@pablonovoa](https://developer.sailpoint.com/discuss/u/pablonovoa)\ **Post date:** [November 4, 2024, 5:46pm UTC](https://developer.sailpoint.com/discuss/t/isc-workflows-fails-to-fail-correctly-in-a-loop/88609/2 "2024-11-04T17:46:54Z")
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 ---
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [November 5, 2024, 8:59am UTC](https://developer.sailpoint.com/discuss/t/isc-workflows-fails-to-fail-correctly-in-a-loop/88609/3 "2024-11-05T08:59:34Z")
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 ---
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [December 4, 2024, 11:12am UTC](https://developer.sailpoint.com/discuss/t/isc-workflows-fails-to-fail-correctly-in-a-loop/88609/4 "2024-12-04T11:12:20Z")
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. ---
**Author:** ![angelo\_mekenkamp](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/angelo_mekenkamp/32/3386_2.png) [@angelo\_mekenkamp](https://developer.sailpoint.com/discuss/u/angelo_mekenkamp)\ **Post date:** [January 14, 2025, 9:11am UTC](https://developer.sailpoint.com/discuss/t/isc-workflows-fails-to-fail-correctly-in-a-loop/88609/5 "2025-01-14T09:11:37Z")
Update from SailPoint Support: > [@SailPoint Support](#): > > I have had an update from the engineering team that the issue has been fixed. > > The JSON marshalling error has been fixed. Now, the user should no longer see the `unexpected end of JSON input` error if the loop step ends at `End Step - Failure`. Instead, the user will see the message set in the `Failure Details` field of the `End Step - Failure`, as shown in the screenshots attached. > > I have verified this fix on my test tenant and it seems to be working at my end. > > Can you please validate the same at your end and let me know in case you have any queries or concerns around this. > > ![image](https://global.discourse-cdn.com/sailpoint/original/3X/e/f/ef0ab8f509bf8464f0df2e1b9e18d55762f083da.png) > ![image](https://global.discourse-cdn.com/sailpoint/original/3X/7/3/73f0fc4d63e0bb1182fada7d05ae11fb974811c6.png) I have no time to build these steps and test this myself on my environment again, so given the screenshots from the environment of SailPoint Support, I will assume it also works on my end. If we come across the issue anyway, we will log another ticket. [@community\_moderators](https://developer.sailpoint.com/discuss/groups/community_moderators), please mark this post of mine as `fixed` as I am not allowed to do this myself.