A different object with the same identifier value was already associated with the session : [sailpoint.object.Link#

[Victor27 (Victor manoel)]

Hello, my company is using IdentityIQ 8.2 and in one of the tasks “synchronize attributes” it reported this error.
A different object with the same identifier value was already associated with the session : [sailpoint.object.Link#ac1046********65]. I would like to know what kind of adjustment or correction I can make in this situation?

[adam_creaney]

I can’t solve this particular problem - but when I have seen this in the past it is usually due to a rule and/or workflow beanshell code trying to update the object (link/account in this case) and then not decaching. Do you have custom rules or scripts associated with any of your synchronized attributes?

[adam_creaney]

it is also not a best practice to update Links directly in logic, last time I implemented anyway. If you do have custom code somewhere, looking for something similar to context.search(Link.class, …) or context.getObjecyById(Link.class) etc

[Victor27 (Victor manoel)]

The error I’m getting is this. In this case, should I make the corrections within some workflow?

[Victor27 (Victor manoel)]

So it means that this is an error is in some workflow?

[iamksatish (Satish Kurasala)]

@Victor27
Is this happening consistently or just a intermittent case?

[amishra97 (Abhinav Mishra)]

@Victor27 What are the options checked on your instance of “Refresh Identity Cube” task?

[Victor27 (Victor manoel)]

yes is giving consistently, every time the task is executed give this error.

[Victor27 (Victor manoel)]

The only thing this task does is Synchronize attributes and Refresh identity attributes. Then every time I perform the task it brings me that error “A different object with the same identifier value was already associated with the session : [sailpoint.object.Link#0a**************9b]”

[jlebron1 (Justin Lebron)]

@Victor27 did you ever get this fixed and if so how?

[aleksander_jachowicz]

Any custom rules in target mapping or target sources?

[MuhammadMustafa]

Hi @Victor27, I’m predicting the following as conclusion:
A. The error is due to duplicate object references in the Hibernate session
B. Avoid loading or modifying the same Link object multiple times
C. Use context.decache() when refreshing objects in custom logic
D. Review any custom rules associated with the Synchronize Attributes task

[gmilunich (Geoff Milunich)]

@Victor27

The only thing this task does is Synchronize attributes and Refresh identity attributes. Then every time I perform the task it brings me that error “A different object with the same identifier value was already associated with the session : [sailpoint.object.Link#0a**************9b]”

Both of those likely call rules or scripts associated with updating the Identity Attributes or workflows that are triggered off of an Identity Attribute Changed Trigger. You’ll likely find a Link object in use in one of those that if not being properly decached. Many times, it is an object getting passed between workflow steps rather than the ID that can cause this. I would review where you are using the Link object in your rules and see if something jumps out at you.

@MuhammadMustafa

Hi @Victor27, I’m predicting the following as conclusion:
A. The error is due to duplicate object references in the Hibernate session
B. Avoid loading or modifying the same Link object multiple times
C. Use context.decache() when refreshing objects in custom logic
D. Review any custom rules associated with the Synchronize Attributes task

Are these suggestions AI-Generated? I believe all of these have been suggested in this topic already.

[MuhammadMustafa]

Hi @gmilunich, Oh, I didn’t read all the replies, so I didn’t realize those points were already mentioned in the thread, my bad!, thanks for pointing it out.
I’ll make sure to read through all replies next time to avoid repeating what’s already been said. once again appreciate the note!

Regards,
Muhammad