Hi All,
I’m exploring sailpoint my own. I have onborded the HR application and other application and enabled the Joiner event. But the problem is when i was ruining the aggregation i can see the joiner has been trigger two times. One is by LCM: spadmin and second one for Refresh identity task. Can any one help with this to understand the problem.(Attached sanpshot).
Check if by any chance the aggregation task is having process events enabled?
Hi @Gutte_Shubham - what is the Joiner trigger? Looks like several days passed between them. Can you verify if the original one completed successfully? Also do you mark joiner complete once it has run?
In the refresh Identity task, you might have process events checkbox tick, which is basically executing the events. The two events screenshot you shared are a week after, do you have any attribute created which basically is updated once the joiner is completed, so that it is not re-processed again??
Hello @naveenkumar3
Thank you for your response.
Yes, i can see in the Refresh identity task the process event checkbox is tick. and the aggregation task as well this is the reason the two joiners are triggers?. how i can fix it.
Hi @bhanuprakashkuruva ,
Yes, the aggregation task and the identity refresh task is having process event enabled. That’s the reason the two joiner is triggers for each endpoint.
Have you done any customizations to the Lifecycle Event - Joiner workflow or is it OOTB?
I remember seeing issues when you save the identity object with triggerSnapshot in it in the workflow. e.g. in the start of a workflow.
@BenjaminIglesias,
This is the OOTB workflow only. there is not any customization.
Okay, remove from aggregation task and run, events will be executed only once. Basically process events will be enabled in refresh task only in maximum cases, in some corner cases that events process will be added in aggregation.
Just uncheck the flag from one of the task or both, and create an attribute which basically gets updated, whenever joiner gets completed on the user, as to avoid the getting triggered again. Create a step at the end to update the attribute, once all the steps are completed as part of your joiner workflow.
