We have found following situation during recon. task checkup.
Reconc task of specific online Resource suspends with fatal error:
Internal Error: Object already exists on the resource: org.identityconnectors.framework.common.exceptions.AlreadyExistsException(User: 'ivanzzz' already exists)
User ivanzzz has projection to this Resource. ShadowType also exists, but contains cached data to be provisioned to resource when online/possible. This is what reconc. is trying to do, create account again. The account also natively exists on the resource, hence we get AlreadyExistsException. Sofar all OK.
Normally when AlreadyExistsException is raised, MP just links the existing account to owner instead of failing fatally. BUT - here when data is cached in the shadow, it does not link and fails. I think it should also LINK the owner and be at peace
Will provide UserType, resource and ShadowType privately.