Is this question regarding a custom connector? If so, please share relevant details below.
No, this question is not regarding a custom connector.
Share all details related to your problem, including any error messages you may have received.
Hi,
Our leaver lifecycle event is not being triggered on a timely manner. it’s taking 2 or 3 days for the user who is terminated already and due to this manager is not being able to receive notification. How can i correct this issue. kindly help
Is your refresh happening frequently and is the event itself triggering late or thought the event triggered your notification is getting delated, I mean do you have any step in workflow where you added a delay, can you share the trigger condition or rule and workflow attached details.
As i was checking the history of the identity. I can see the leaver date was on 1st nov 2023. but the successfactor changed from active to terminated on 2nd nov. is there an issue with this because we received it as an issue from client that why the termination started on 2nd nov when the date was mentioned as 1st nov. what we can do in such cases?
I checked the leaver workflow don’t see any wait period. Also, the refresh task frequency is atleast 4 time per day and successfactor also aggregates atleast 2 times as well. kindly help how can i validate on this issue?
Hey Amit, are the other application account removal/deactivation running on time as part of the leaver workflow or is it just successfactors which is being delayed? Also, in the events section on the identity cube, when did the leaver occur on the identity?