Identity Refresh Job Behavior

I encountered a scenario where Active Directory (AD) account provisioning failed.

I expected that the Identity Refresh Job would refresh the identity and reattempt the failed AD provisioning. However, no event was triggered for the user the following day. Next day when I manually processed the identity, the AD provisioning was completed successfully.

Could anyone provide insights into why the Identity Refresh Job did not retry the failed provisioning automatically?

Additionally, I would like to know if there is a way to pause the Identity Refresh Job in case of an issue or if the job gets stuck, and how we can clear the job when needed.

Any guidance would be greatly appreciated.
Thank you!

Hi,

How you are trying to provision AD account?

Ideally it should create account on next refresh. Below is the documentation on refresh task.

We cannot pause the identity refresh job.

-Abhinov

1 Like

Thank you @Abhinov7
Also I am exploring additional options to gain better control over the Identity Refresh Job in case of errors or data issues.

You can manually trigger the identity refresh but cannot control the identity refresh process which is taken care by SailPoint.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.