# How to tackle a failed native change detection workflow?

**URL:** <https://community.sailpoint.com/discuss/t/how-to-tackle-a-failed-native-change-detection-workflow/32608>\
**Category:** Lifecycle & Governance\
**Tags:** identityiq-8.3, compliance, event-triggers-workflows\
**Created:** [January 15, 2024, 9:48am UTC](https://community.sailpoint.com/discuss/t/how-to-tackle-a-failed-native-change-detection-workflow/32608 "2024-01-15T09:48:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pritishmhrn](https://sea3.discourse-cdn.com/sailpoint2/discuss/user_avatar/community.sailpoint.com/pritishmhrn/32/16734_2.png) [@pritishmhrn](https://community.sailpoint.com/discuss/u/pritishmhrn)\
**Post date:** [January 15, 2024, 9:48am UTC](https://community.sailpoint.com/discuss/t/how-to-tackle-a-failed-native-change-detection-workflow/32608/1 "2024-01-15T09:48:11Z")

</div>

Hello All,

We have a workflow to revoke unwanted accesses which gets detected via Native Change Detection, once the workflow gets launched the snapshot gets removed from debug page of the identity which will not allow us to retrigger the workflow.

In cases of workflow provisioning failure, how do we tackle ( considering the snapshot getting removed )?

Please share your experiences based on project implementation. One custom solution I can think of is tracking such failures via audit events and running a scheduled task to grab such → create a provisioning plan and retry those.

[@Bernie](https://community.sailpoint.com/user/145)&nbsp;any inputs based on your experience. Apologies to copy you as none has responded. 😞

Thanks and regards

---

<div class="post-metadata">

**Author:** ![Bernie](https://sea3.discourse-cdn.com/sailpoint2/discuss/user_avatar/community.sailpoint.com/bernie/32/16974_2.png) [@Bernie](https://community.sailpoint.com/discuss/u/Bernie)\
**Post date:** [January 22, 2024, 3:32pm UTC](https://community.sailpoint.com/discuss/t/how-to-tackle-a-failed-native-change-detection-workflow/32608/2 "2024-01-22T15:32:51Z")

</div>

I’m not sure how your workflow is configured. Is the “enableRetryRequest” variable enabled?&nbsp; Was optimistic provisioning enabled?

---

<div class="post-metadata">

**Author:** ![pritishmhrn](https://sea3.discourse-cdn.com/sailpoint2/discuss/user_avatar/community.sailpoint.com/pritishmhrn/32/16734_2.png) [@pritishmhrn](https://community.sailpoint.com/discuss/u/pritishmhrn)\
**Post date:** [March 31, 2024, 11:28am UTC](https://community.sailpoint.com/discuss/t/how-to-tackle-a-failed-native-change-detection-workflow/32608/3 "2024-03-31T11:28:21Z")

</div>

Hello. Thank you! I received a feedback from Menno on the wiki page:

[https://community.sailpoint.com/t5/IdentityIQ-Articles/Native-Change-Detection/ta-p/72848/page/2/show-comments/true](https://community.sailpoint.com/topic/72848)

and also kept the provisioning retry variable in the workflow to solve the above.