# Retry for Failed Provisioning

**URL:** <https://developer.sailpoint.com/discuss/t/retry-for-failed-provisioning/1565>\
**Category:** SHF Discussion and Questions\
**Created:** [September 15, 2021, 12:34pm UTC](https://developer.sailpoint.com/discuss/t/retry-for-failed-provisioning/1565 "2021-09-15T12:34:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![aashish\_Singhal](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@aashish\_Singhal](https://developer.sailpoint.com/discuss/u/aashish_Singhal)\
**Post date:** [September 15, 2021, 12:34pm UTC](https://developer.sailpoint.com/discuss/t/retry-for-failed-provisioning/1565/1 "2021-09-15T12:34:48Z")

</div>

Hi,  
I am using IDN . we have to configure provision retry in case if provisioning failed

---

<div class="post-metadata">

**Author:** ![AnamicaShroti](https://avatars.discourse-cdn.com/v4/letter/a/ad7895/32.png) [@AnamicaShroti](https://developer.sailpoint.com/discuss/u/AnamicaShroti)\
**Post date:** [February 18, 2022, 5:52am UTC](https://developer.sailpoint.com/discuss/t/retry-for-failed-provisioning/1565/2 "2022-02-18T05:52:49Z")

</div>

Hi @aashish_Singhal

In case provisioning fails, it is retried in next role or identity refresh by IDN itself.

Regards,  
Anamica

---

<div class="post-metadata">

**Author:** ![yannick\_beot](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/yannick_beot/32/8985_2.png) [@yannick\_beot](https://developer.sailpoint.com/discuss/u/yannick_beot)\
**Post date:** [February 18, 2022, 2:23pm UTC](https://developer.sailpoint.com/discuss/t/retry-for-failed-provisioning/1565/3 "2022-02-18T14:23:06Z")

</div>

Hello @aashish_Singhal,  
In addition what @AnamicaShroti said, it is possible to define retryable error at the connector level.

For instance, for the generic Web service connector, you can define the parameter `possibleHttpErrors` as described in :  
[https://documentation.sailpoint.com/connectors/webservices/help/integrating\_webservices/additional\_configuration\_parameters.html](https://documentation.sailpoint.com/connectors/webservices/help/integrating_webservices/additional_configuration_parameters.html)

You have to look at the connector documentation for this.

---

<div class="post-metadata">

**Author:** ![whoiscjay](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/whoiscjay/32/12806_2.png) [@whoiscjay](https://developer.sailpoint.com/discuss/u/whoiscjay)\
**Post date:** [April 3, 2023, 10:18pm UTC](https://developer.sailpoint.com/discuss/t/retry-for-failed-provisioning/1565/4 "2023-04-03T22:18:46Z")

</div>

Hi @AnamicaShroti , I wasn’t able to find any documented reference (in the Admin Guide) to the role/identity refresh processes initiating a retry for provisioning failures. Each provisioning process in the Admin guide has its retry process documented, however there is noting that states that refresh initiates a retry. Is this something that can be updated?

---

<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:** [July 19, 2023, 2:22pm UTC](https://developer.sailpoint.com/discuss/t/retry-for-failed-provisioning/1565/5 "2023-07-19T14:22:05Z")

</div>

Closed on July 19, 2023, 2:22pm UTC