We are facing an issue with Workday to Okta user provisioning for a new joiner. The Workday import runs successfully, but the user does not match or create properly in Okta.

In Import Results, the status shows:

• NO Okta user matches found
• Username/Email populated as Timeout@WorkdayImport.com
• No AD / Okta account gets created
• AAP / provisioning checks show no import logs for the user

Workday profile was re-created by HR/Tier 2, but the issue persists. We observed that some mandatory attributes (e.g., Cost Center) may have been missing at initial hire, though they have since been updated.

Has anyone encountered a scenario where Workday import creates a placeholder user with Timeout@WorkdayImport.com, and even after correcting Workday data, Okta still fails to reprocess or provision the account automatically?

What is the recommended remediation?

Any guidance or best practices would be highly appreciated.