Hello everyone,
I noticed this morning that some identities have not been refreshed to update their lifecycle status. It should have been updated 2 days ago, I had to do a “Process Identity” manually. I also tried updating the identity profile to do a mass refresh and it worked, but why doesn’t this happen automatically every day?
Thanks for your help.
Regards,
Mathieu G.
Hi @mathieug , identities refresh should run twice daily as part of the scheduled identity processing. I would raise it with SailPoint support first to save some time and then try to look more into it.
Its failing in my sandbox tenant. And I’ve raised a ticket with SP.
A LCS change stops an attribute sync from happening.
Also, I think that scheduled processing has been phased out in preference to event based processing
“Scheduled” processing isn’t completely being phased out, it is just becoming more controllable by the customer. Each identity will have an attribute called “Next Processing Date” that will indicate the ISO 8601 date and time that the processing should occur for each users. Each organization will be able to set the value according to their needs. For example, it could be set to 5 p.m. in the identity’s local timezone to start the deprovisioning process at the close of business on their last day of work.
Hi,
After analyze, it appears that the concerned identities was in inactive state (INACTIVE_LONG_TERM). This explains why they were not processed.
Regards,
Mathieu G