hi @sureshbommareddy98 this usually happens when the same user is being processed by multiple workflows in parallel.
What you’re seeing is expected if:
-
LCM Scheduler triggers a refresh (for population / identity refresh), and
-
Request Handler processes an LCM event for the same identity around the same time
Both paths can evaluate the same rule, causing it to fire more than once, even if the condition logically “shouldn’t”.
I would to check / fix:
-
Ensure the rule is idempotent (add a guard flag like a custom identity attribute or request attribute to prevent re‑execution)
-
Check if Identity Refresh is enabled in LCM workflows (often overlooked)
-
Avoid running scheduled refresh + LCM request simultaneously for the same users
-
Add logging to confirm whether the trigger is coming from
LCMProvisioningvsIdentityRefresh
Solution is usually not changing the condition, but preventing duplicate execution paths.
Hope this helps.
The issue is happening only for one user, not for all users. The event is still triggering multiple times even when the Identity Refresh task is turned off.
@sureshbommareddy98 If it’s happening only for one user, then this is almost never a scheduler issue.
A few things I’ve seen cause this:
-
A stuck or retrying LCM request for that user
-
Some identity attribute on that user is being updated repeatedly, which keeps firing the same event
-
The user is part of multiple populations or workflows, so the same rule is being evaluated more than once
-
A custom rule/workflow that triggers on identity save, not just refresh
At this point, I would recommend:
-
Checking pending / failed LCM requests for that identity
-
Adding a simple guard check (like a custom identity flag) so the rule runs only once
-
Adding a bit of logging to see exactly which workflow path is triggering it
When it’s limited to a single user, it’s almost always a data or stuck‑request scenario, not a product bug.
Hope this helps narrow it down 
Can you please confirm if the triggerSnapshots tag gets removed from the user once one event gets triggered.
As we have seen this problem in client env where the event was triggering again and again after the refresh.
Solution was provided by SailPoint Support for this. Please confirm the first statement.
Thanks
Manish Singh
@sureshbommareddy98 Please run the Identity Refresh with Process EVents option selected. If the event triggers and snapshot is not removed then let me know.
@sureshbommareddy98 Are you using a IdentityTrigger rule as an event type? If yes, could you please share it here.
@sureshbommareddy98 If it is happening for only one user, then you need to check the trigger rule that you have applied to the Lifecycle Event. That rule might be including the user everytime whenever the refresh runs.
The event is being triggered for that user even though the condition is not actually met. I added logs and checked — the code is still going inside the “true” condition block. I’m not sure how that’s happening when the condition should be false.
Can you please share the rule.