# Access request - Source not available

**URL:** <https://developer.sailpoint.com/discuss/t/access-request-source-not-available/20979>\
**Category:** SHF Discussion and Questions\
**Tags:** sailpoint-identity-security\
**Created:** [November 16, 2023, 12:39pm UTC](https://developer.sailpoint.com/discuss/t/access-request-source-not-available/20979 "2023-11-16T12:39:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manju22](https://avatars.discourse-cdn.com/v4/letter/m/45deac/32.png) [@Manju22](https://developer.sailpoint.com/discuss/u/Manju22)\
**Post date:** [November 16, 2023, 12:39pm UTC](https://developer.sailpoint.com/discuss/t/access-request-source-not-available/20979/1 "2023-11-16T12:39:08Z")

</div>

Hi ,

If the webservice source is not available due to maintenance, what will happen to the access request submitted for the Entitlement/Access profile? If the provisioning fails, will it re-try once the source is up?

Thanks,

---

<div class="post-metadata">

**Author:** ![KRM7](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/krm7/32/2685_2.png) [@KRM7](https://developer.sailpoint.com/discuss/u/KRM7)\
**Post date:** [November 16, 2023, 2:16pm UTC](https://developer.sailpoint.com/discuss/t/access-request-source-not-available/20979/2 "2023-11-16T14:16:49Z")

</div>

That depends on the connector, check Additional settings in your source configuration.

We can define for which error messages, retry should work.

---

<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:** [November 16, 2023, 4:38pm UTC](https://developer.sailpoint.com/discuss/t/access-request-source-not-available/20979/3 "2023-11-16T16:38:41Z")

</div>

> [@KRM7](#):
>
> We can define for which error messages, retry should work.

I believe this is the document that @KRM7 is referring to.

> **[Provisioning Overview - SailPoint Identity Services](https://documentation.sailpoint.com/saas/help/provisioning/index.html#errors-and-retries)**
>
> SailPoint Identity Services Documentation

---

<div class="post-metadata">

**Author:** ![edmarks](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/edmarks/32/2896_2.png) [@edmarks](https://developer.sailpoint.com/discuss/u/edmarks)\
**Post date:** [November 16, 2023, 7:19pm UTC](https://developer.sailpoint.com/discuss/t/access-request-source-not-available/20979/4 "2023-11-16T19:19:02Z")

</div>

IDN is more of a Fire/Forget provisioning model with some basic retry options. This is VERY different than other IAM vendors that approach this as actual state vs. desired state and continually generate provisioning tasks to close the difference between actual and desired state.

---

<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:** [January 15, 2024, 7:19pm UTC](https://developer.sailpoint.com/discuss/t/access-request-source-not-available/20979/5 "2024-01-15T19:19:40Z")

</div>

Closed on January 15, 2024, 7:19pm UTC

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