Let me preface this by saying I previously opened a support case for this item and it went nowhere, after months of collaboration between Okta and Workday, and the respective teams internally that manage both, but I'm at my wit's end and the business is demanding a resolution.

Essentially, sometimes -- not always, but pretty frequently, we see an issue where future-dated conversions from contractor\contingent worker to employee results in the user's Okta account being completely disabled indefinitely, until they call in to report their lack of access. At that time, the tried and true "fix" is to run a manual import from within the Okta Workday app. We'll then see a rash of reactivations with employeeType changes.

So to summarize, the contract end date arrives, which causes the account to deactivate. This is normal behavior in the course of a conversion, but what is ABNORMAL is that the account doesn't immediately reactivate as an employee. This doesn't happen until a full manual import is run. Note also that even a schedule import doesn't reactivate the records -- that was one thing that was uncovered during the previous support request, and we learned that scheduled imports are incremental where a manual is full, and seemingly that matters here.

Has anyone been through this, and come up with a lasting solution? There's some further collateral damage in that the time deactivated ends up triggering a deprovisioning event for several downstream apps, all group memberships are lost, etc.