Few Entitlement's are not able to access we are getting error

[mrahulbb (Mekala Rahul)]

we have updated all the entitlement’s Requestable to false, only 16 entitlement’s are not able to set to false are those are true and when we tried to open they are throwing error ERROR: Trace ID: 99d1b50884c841cd90c82dd263edb92d Details: An error occurred. Please contact your administrator. The server did not find a current representation for the target resource.

More than 1lakhs entitlement’s are update and are able to access but only 16 were unable to open and unable to access getting above error

[Sachin_Rajathadri]

Hi Mekala,

Have you tried using the entitlement API to set them to False? Here’s the link to that api - patch-entitlement | SailPoint Developer Community

If it still doesn’t work, try to reset the source entitlements and aggregate again. Here’s the api to that - reset-source-entitlements | SailPoint Developer Community

Hope this helps!

[nandambk (Karthik Nandam Balraj)]

@mekala,

Based on the error i think of the these entitlements might been removed or renamed. You can find in the below forum where they worked with support team to make work it in the backend

PATCH /beta/entitlements:id fails on entitlements without "current representation"

That’s actually how I found the issue. When we decided we wanted to try requestable entitlements, we found about 80,000 of them had been set to requestable by the system. I used the /beta/entitlements/bulk-update API to work through those, but found some stragglers. I worked through the remaining entitlements one by one with the /update API. The /beta/entitlements/bulk-update executes without error, but has no effect on these entitlements. In short, they’re requestable and they’re staying that…

[jsosa (Julian Sosa)]

Hi Makela. As entitlements could have been deleted on source or have some problem, you should try using the private api to reset aggregated entitlements (this call is active at the moment but should be migrated soon to beta/v3):

cc/api/source/reset/_private_source_id

Then you can reaggregate and mark the entitlements as requestable again.

Other option is to open a case in Support. In fact this solution was given to me in a case, very similar to yours opened about 3 months ago.

[cgurung (Chhiring Gurung)]

Hi Mekala,

We have exact same issue in our prod tenant and we opened up a case with SailPoint Support, escalated it and finally after 12 days, today they removed those entitlement from our system. In ticket they mentioned they identify this as a bug and their engineering team is working on it. At this point of time there was not ETA provided.
Your best approach would be open a case with Support and work with them to clean up these entitlements.