<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5WR000016KWsq0AGOkta Classic EngineLifecycle ManagementAnswered2025-12-31T17:15:31.000Z2025-12-23T06:36:52.000Z2025-12-31T17:15:31.000Z

MarxW.15267 (Customer) asked a question.

Preventing Workday LCM from reactivating users deactivated via Okta Workflows

Hi everyone, I am currently designing an Okta Workflow to offboard users at their specific last working hour, rather than relying on the standard Workday integration (which typically triggers after the first scheduled import following their last day).

 

While the workflow successfully deactivates the user at the intended time, I’ve encountered an issue: the Workday connector reactivates the Okta account during the next scheduled import because the user is still marked as "Active" in Workday. I cannot disable the reactivation setting as it is required for our rehire process.

Does anyone know of a way to ensure that a user deactivated via Workflows remains deactivated and is not overwritten by the LCM sync?

 

Thank you for your help!


  • Mihai N. (Okta, Inc.)

    Hi @MarxW.15267 (Customer)​ , Thank you for reaching out to the Okta Community! 

     

    I haven't seen this use case being implemented or discussed in conjunction with Workflows, but if you haven't already, I recommend checking the baked-in Workday Real-Time Sync feature.  

    If you still need to look into a specific Workflows solution, please check in with the dedicated Okta Workflows Discussion Group, to see if anyone there can offer some insight. Our colleagues also have weekly community office hours , where you can check with them.  

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Collect them all. Learn a new skill and earn a new Okta Learning badge.

    Just released: More Okta Community badges just added

    AMA Alert: Starting the Year Strong with Stronger Authentication (MFA) Adoption

    Expand Post
    Selected as Best
  • RohitU.50441 (Trevonix)

    Deactivation outside of connector becomes sort of hackey.

     

    There is no easy way to do it.

     

    If you really want to achieve it the best way is to handle deactivation and reactivation both using Workflows and completely turning off connector deactivation option.

     

    Hybrid has its flaws. For ex, you can assign users to a particular group and when the import job completes trigger a flow that checks if a user is member of that group and deactivate again.

     

    This method will activate user briefly but you force deactivation again using group membership. But again not compliant and hackey.

    Expand Post

Loading
Preventing Workday LCM from reactivating users deactivated via Okta Workflows