Error while enabling account

[gmilunich (Geoff Milunich)]

@NandanaGopu

You’re changing the Lifecycle State in SailPoint IDN, expecting it to trigger provisioning actions (like disabling/enabling an account) based on the Identity Profile’s Provisioning Policy, but instead:

• The Lifecycle State change shows as a pending Account Activity
• It never progresses or completes
• No actual enable/disable action happens

This is a common headache in IDN setups, especially when combining Lifecycle States, Provisioning Policies, and Web Service connectors.

Let’s break it down and walk through possible causes and fixes.
…

This appears to be AI-Generated content and it is considered poor etiquette to just post AI responses like this. AI can be used to help you develop or check your response, but your response should be in your own words.

Additionally, in this case, your response does not appear to answer the question, and does not take in the information already presented.

On a second glance, it does not appear to discuss the issue the user is seeing at all, so it is not really helpful to this situation.

[nileshnikalje]

I raised a Sailpoint support ticket and they were able to debug and fix the issue on the sandbox tenant. Post their fix, i was able to perform all the operations as expected. AS per the ticket information, this was an issue on the sandbox tenant and is not expected to occur on production.

[nileshnikalje]

@gmilunich

hat you don’t handle the identity directly in your code, it is likely there is something going on internally that is causing the process to close the session before the identity is done. Do you have a custom Before/After operations on your webservice connector (Assuming this is the DIrect Connector and not

Yes it is a direct connector with before operations rules configuration. Sailpoint’s engineering team was able to resolve it via a ticket

[Arshad (Arshad Moghul)]

@nileshnikalje

I raised a Sailpoint support ticket and they were able to debug and fix the issue on the sandbox tenant.

@nileshnikalje Its great to know that this was fixed by SailPoint.

Just curious to know the root cause, have they provided a background of why we were seeing the error “An unexpected error occured: failed to lazily initialize a collection of role”?

[nileshnikalje]

No. They havent. They just mentioned that the issue is fixed by the engineering team and confirmed that this affected the SB tenants and not the prod ones.

[Arshad (Arshad Moghul)]

@nileshnikalje

confirmed that this affected the SB tenants and not the prod ones.

This is informative, thank you for confirming!

[gmilunich (Geoff Milunich)]

Great to know it was resolved. I know you mentioned that they did not disclose the root cause of the issue, but did they change, or ask you to change any part of your code to help with this?

[nileshnikalje]

They didnt asked me to change anything on my side, neither they have disclosed what changed they did if any on their side. Just informed that they fixed it at their side.