Share all details related to your problem, including any error messages you may have received.
Hi Community,
Suddenly I am getting this error in refresh identity cube task " Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) : [sailpoint.object.IdentityEntitlement#0a013c39897712aa81897e7fd334115c] ". When I checked under debug’s identity entitlement, I got the user and the entitlement. When I checked in the users application account the application is not there but initially it was there, have no idea how that got removed and what is the solution for this issue kindly help.
If your code is being accessed by multiple threads at the same time.
How are you creating session object?
So if there are multiple threads accessing the same session and trying to update the same database entity, your code can potentially end up in an error situation like this.
So what happens here is that more than one threads try to update the same entity, one thread succeeds and when the next thread goes to commit the data.
The error you’re encountering during the “refresh identity cube task” in SailPoint indicates a classic concurrency issue or a stale state problem. This type of error, Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect), often occurs when the database record the task is attempting to access has been changed or deleted by another process between the time it was read and the time the operation was attempted. Here’s how you can approach resolving this issue:
Review Logs: Check the application logs for any other processes that might be interacting with the same data (Identity Entitlements in this case) at the same time. This can include other scheduled tasks, updates triggered by API calls, or manual changes.
Check Scheduled Tasks: Verify if there are overlapping tasks that might modify entitlements or application accounts.