Hi Team
After reinstating any user in SailPoint, we could see triggerSnapshot exist in the identity.
We expect that the triggerSnapshot should be removed after the event is processed successfully.
Have anyone faced this issue? Any inputs on what setting/configurations to be checked for the removal of trigger snapshot would be helpful.
Thanks
Divya M
Hello Divya. First, confirm whether the identity refresh task has Process Events enabled (processTriggers=true). Without that, the lifecycle event may not be processed and the snapshot can remain on the identity.
If it is already enabled, check the refresh and workflow logs for errors. Also check whether the triggered workflow saves or commits an identity object while the event is still being processed, or changes an attribute involved in the trigger, as that could retain or recreate triggerSnapshots.
Could you share the lifecycle event configuration and identity refresh task settings?
@DivyaSubha I haven’t run into this personally, but as far as I know, the triggerSnapshot attribute is typically used internally by ISC to process lifecycle events. Once the event completes successfully, it should normally be cleared automatically.
If it’s still present after the reinstatement has finished, I’d start by checking whether the lifecycle event or associated workflow completed successfully. It’s also worth reviewing the workflow execution logs for any errors or pending steps that might have prevented the cleanup.
If everything appears to have completed successfully and the triggerSnapshot is still not being removed, it could be worth opening a SailPoint Support case, as this may indicate an issue with the event processing rather than a configuration problem.
@DivyaSubha Similar Issue: TriggerSnapshots not cleared after identity refresh causing repeated trigger execution - IdentityIQ (IIQ) / IIQ Discussion and Questions - SailPoint Developer Community
As per the post, it got resolved after removing Synchronize Attribute option.