
zk01e (zk01e) asked a question.
Hello OKTA Community!
I'm encountering a challenge with our OKTA Real Time Sync (RTS) setup regarding future-dated terminations.
Scenario - A worker is terminated with both a future-dated Term Effective Date and Last Day of Work.
Configuration - I've added two immediate termination reason reference IDs from Workday into the OKTA configuration. Although our OKTA RTS setup works as expected in other scenarios, for this particular case, we adjusted the termination business process to include a step delay, aligning the OKTA RTS step with the Last Day of Work date.
Issue - Despite configuring a step delay for the RTS to activate on the actual Last Day of Work (which is in the future), OKTA RTS is deactivating the account immediately on the day the termination is entered, not on the future date as intended.
Question - Is it standard behavior for OKTA RTS to ignore the step delay and proceed with immediate deactivation when immediate termination reasons are specified, even if a delay is configured? I was under the impression that adding a step delay would postpone the deactivation until the Last Day of Work. Could someone clarify if this behavior is expected and advise on how to achieve the desired delay?
Appreciate any insights or guidance on this issue. Thank you!

Hello @zk01e (zk01e) Thank you for reacting out to our Community!
As per our documentation:
Please also see out full documentation below:
https://help.okta.com/en-us/content/topics/provisioning/workday/workday-provisioning.htm#Deactiva
--
Subscribe Today: The Okta Community is on YouTube
Hi Paul,
Thank you very much for your prompt reply and for providing further details.
After multiple reviews of the documentation, I understand that we've introduced a step delay in the termination process within Workday. However, it seems the crux of the issue lies in how the system handles the matching termination reason—specifically, whether it fails to recognize it or intentionally overlooks it due to a direct match with an immediate termination reason. Could you confirm if my understanding is correct?
Given this, I'm curious about the recommended approach for handling future-dated immediate terminations. The concept might seem unconventional—planning an 'immediate' termination for a future date—but is it feasible within our current framework? Or is the more appropriate solution to define a new, distinct termination reason tailored to these cases?
I appreciate your guidance on navigating this scenario.
Best regards,
John
It actually sounds like we may not need to include any immediate termination reasons at all in OKTA which should meet the requirements still (if future-dated)
Hello @zk01e (zk01e) I would recommend to reach out to Support for additional assistance on this matter, and they should be able to provide additional guidance with this issue.
--
Subscribe Today: The Okta Community is on YouTube