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.
3 Likes
Yes it is a direct connector with before operations rules configuration. Sailpoint’s engineering team was able to resolve it via a ticket
@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”?
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.
1 Like
This is informative, thank you for confirming!
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?
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.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.