# Debug Workflow loop inner steps

**URL:** <https://developer.sailpoint.com/discuss/t/debug-workflow-loop-inner-steps/30252>\
**Category:** SHF Discussion and Questions\
**Tags:** workflows, identity-security-cloud\
**Created:** [February 13, 2024, 4:51pm UTC](https://developer.sailpoint.com/discuss/t/debug-workflow-loop-inner-steps/30252 "2024-02-13T16:51:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nadim](https://avatars.discourse-cdn.com/v4/letter/n/9dc877/32.png) [@Nadim](https://developer.sailpoint.com/discuss/u/Nadim)\
**Post date:** [February 13, 2024, 4:51pm UTC](https://developer.sailpoint.com/discuss/t/debug-workflow-loop-inner-steps/30252/1 "2024-02-13T16:51:07Z")

</div>

When looking into a workflow execution history we found an event stating that a workflow Task failed.

We have pinpointed that the failed task is generated by a step that is inside a loop in our original workflow.

We are unable to find a way to display a step by step execution of the loop operations in our workflow execution to be able to debug the source of the error.  
I have the workflow ID and the run ID of the loop executions that generated child workflows. Is there a way to make use of these two values in order to see the issue more clearly?

Best regards

---

<div class="post-metadata">

**Author:** ![mehuljogi](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/mehuljogi/32/8264_2.png) [@mehuljogi](https://developer.sailpoint.com/discuss/u/mehuljogi)\
**Post date:** [February 28, 2024, 2:23pm UTC](https://developer.sailpoint.com/discuss/t/debug-workflow-loop-inner-steps/30252/2 "2024-02-28T14:23:15Z")

</div>

Hello Nadim El Khoury,

Try using [wehbook](https://webhook.site/) for debugging inside the loop under the workflow.  
The following blog may be helpful for debugging with Webhook:

> [@Testing Workflows in IdentityNow Using Webhook.site](https://developer.sailpoint.com/discuss/t/testing-workflows-in-identitynow-using-webhook-site/12868):
>
> Workflow Testing with Webhooks In this blog post, I will be explaining how webhooks can be leveraged in IdentityNow to obtain and test workflow output. Testing workflow output is crucial for ensuring the smooth operation and creation of Workflow. In this article, we’ll dive into webhooks and provide a step-by-step guide to help you get started. WARNING: webhook.site is a third party website. Please be careful with the data you send to it. It is not recommended to use …

---

<div class="post-metadata">

**Author:** ![Nadim](https://avatars.discourse-cdn.com/v4/letter/n/9dc877/32.png) [@Nadim](https://developer.sailpoint.com/discuss/u/Nadim)\
**Post date:** [February 28, 2024, 2:55pm UTC](https://developer.sailpoint.com/discuss/t/debug-workflow-loop-inner-steps/30252/3 "2024-02-28T14:55:33Z")

</div>

Hello Mehul,

Thank you for your answer, we do use webhooks for debugging when we want to configure new workflows.

Unfortunately in my case the error happened in a workflow we already deployed to production. We do not keep webhooks in our production environment.

Thank you for the suggestion.  
Nadim

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [March 1, 2024, 8:43pm UTC](https://developer.sailpoint.com/discuss/t/debug-workflow-loop-inner-steps/30252/4 "2024-03-01T20:43:48Z")

</div>

Hi Nadim. If you download the execution report for the particular execution that failed, the report will contain the information for every iteration of the loop that ran. You can explore this report file to figure out which loop iteration failed. The error message may not clearly indicate why it failed, so you may have to examine the inputs/outputs of the loop iteration that failed to understand what happened.

 ![image](https://global.discourse-cdn.com/sailpoint/original/2X/5/578870fb4eb345ace5811ba4c12711998b362c0f.jpeg)

---

<div class="post-metadata">

**Author:** ![Nadim](https://avatars.discourse-cdn.com/v4/letter/n/9dc877/32.png) [@Nadim](https://developer.sailpoint.com/discuss/u/Nadim)\
**Post date:** [March 4, 2024, 2:34pm UTC](https://developer.sailpoint.com/discuss/t/debug-workflow-loop-inner-steps/30252/5 "2024-03-04T14:34:23Z")

</div>

Hi Colin,  
This is exactly what we did before creating this post. And as you mentioned we only had information about the loop input without understanding what really happened inside the loop.

I will mark your reply as a solution but unfortunately it did not work in our case because we needed more details to really understand what happened.

Best regards,

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [May 3, 2024, 2:35pm UTC](https://developer.sailpoint.com/discuss/t/debug-workflow-loop-inner-steps/30252/6 "2024-05-03T14:35:04Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
