Hi all,
I noticed that when I refresh an Identity with the Process Events option checked, the logs in the IdentityTrigger rule were being produced twice. This means the rule is being called twice.
Is there a reason behind this?
Thanks in advance
Hi all,
I noticed that when I refresh an Identity with the Process Events option checked, the logs in the IdentityTrigger rule were being produced twice. This means the rule is being called twice.
Is there a reason behind this?
Thanks in advance
Hi @rishavghoshacc ,
Please check your life cycle events if you configure the same rule for other events as well or might have added the same rule for the Include identities rule options.
Dear Rishav,
Kindly check the ‘doRefresh’ attribute in your LCM workflow, as refreshing an identity after successful completion of the first LCM event could cause it. Make sure the trigger condition doesn’t match again.
Or check if any other event is causing to refesh the identity again.
@Saket95606 The problem is that the LCM workflow does not trigger. This is because the trigger condition requires a change in value of the prevIdentity and newIdentity.
Because the rule is being called twice, the change is registered the first time but not during the second call and hence not triggering the workflow
If possible kindly share the detailed logs for better understanding of your problem.