# Does Active Directory source have retry error mechanism?

**URL:** <https://developer.sailpoint.com/discuss/t/does-active-directory-source-have-retry-error-mechanism/78672>\
**Category:** SHF Discussion and Questions\
**Tags:** sailpoint-identity-security, sources\
**Created:** [August 28, 2024, 4:13pm UTC](https://developer.sailpoint.com/discuss/t/does-active-directory-source-have-retry-error-mechanism/78672 "2024-08-28T16:13:50Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Amrit1897](https://avatars.discourse-cdn.com/v4/letter/a/65b543/32.png) [@Amrit1897](https://developer.sailpoint.com/discuss/u/Amrit1897)\
**Post date:** [August 28, 2024, 4:13pm UTC](https://developer.sailpoint.com/discuss/t/does-active-directory-source-have-retry-error-mechanism/78672/1 "2024-08-28T16:13:50Z")

</div>

I have tried adding retryableErrors list in AD source but it does not work.

```auto
"retryableErrors": [
            "Server is not operational",
            "Connect to APP gateway failed",
            "Authentication Failed"
        ],

```

It gets saved from VS code but as soon I close and open source config retryableErrors vanishes, which I believe makes sense as it does not have anything called Retry Error List in UI like ServiceNow source has in Advanced Settings.

So, how can we retry the errors for AD source if retryableErrors list can’t be added?  
I know timeout error can be achieved as per below url.

> **[Timeout Errors and Settings](https://documentation.sailpoint.com/connectors/active_directory/help/common/identitynow_topics/timeout_errors.html)**
>
> SailPoint Connectors Documentation

But if I want some specific error to be retry how this can be achieved?

---

<div class="post-metadata">

**Author:** ![Anshu\_Kunal](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/anshu_kunal/32/14680_2.png) [@Anshu\_Kunal](https://developer.sailpoint.com/discuss/u/Anshu_Kunal)\
**Post date:** [August 28, 2024, 4:17pm UTC](https://developer.sailpoint.com/discuss/t/does-active-directory-source-have-retry-error-mechanism/78672/2 "2024-08-28T16:17:25Z")

</div>

Check this post for configuring retries on sources

> [@How to Configure Retries for Connector Aggregations and Provisioning Actions](https://developer.sailpoint.com/discuss/t/how-to-configure-retries-for-connector-aggregations-and-provisioning-actions/63485):
>
> Overview Connectors in both IdentityIQ and Identity Security Cloud support retryable errors during both aggregation and provisioning. This document showcases how to configure these. Keep in mind retries can happen at the platform /Identity Security Cloud level(distinct) to what can happen at the ‘connector’ level. There are many points on retries, most provisioning actions are retriable, but some connectors do have fidelity around which errors can be set as retriable Aggregation Retries Identi…

---

<div class="post-metadata">

**Author:** ![Amrit1897](https://avatars.discourse-cdn.com/v4/letter/a/65b543/32.png) [@Amrit1897](https://developer.sailpoint.com/discuss/u/Amrit1897)\
**Post date:** [August 30, 2024, 1:40am UTC](https://developer.sailpoint.com/discuss/t/does-active-directory-source-have-retry-error-mechanism/78672/3 "2024-08-30T01:40:57Z")

</div>

@Anshu_Kunal, Thanks for the response.  
I am able to add retryableErrors, provisioningRetryThreshold and provisioningMaxRetries. Testing also worked but not properly.

For testing retryableErrors, I am adding error like _Authentication Failed_ in the retryableErrors list.  
Basically I have provided unregistered iqservice user, then disabled the account which fails with _Authentication Failed_ error. Then added this error in retryableErrors list and also added provisioningRetryThreshold and provisioningMaxRetries. I thought running manual identity refresh will retry the error which does not happen. Then I disabled the user again and in the mean time fixed the error by correcting iqservice user, which disabled the account but it was in pending sate from long time and took more than usual time to disable.

So, am I doing testing correctly/this is how am I suppose to test?  
Or is there any better way to test retryableErrors?

---

<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:** [October 29, 2024, 1:40am UTC](https://developer.sailpoint.com/discuss/t/does-active-directory-source-have-retry-error-mechanism/78672/4 "2024-10-29T01:40:59Z")

</div>

Closed on October 29, 2024, 1:40am UTC

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