Hello @YudhoP.49573 (Customer)​ Thank you for posting on our Community page!

This is a known and incredibly frustrating edge case with Workday-to-Okta integrations. You are absolutely on the right track regarding the missing mandatory attributes at the time of the initial hire.

Here is exactly what is happening behind the scenes and the step-by-step remediation to fix it.

The Root Cause: WhyTimeout@WorkdayImport.com?

This placeholder email/username typically appears when Workday takes too long to return a Calculated Field (often the Primary Work Email or Username) during the API call, or when a missing mandatory attribute causes Okta's mapping expression to fail and fall back to a default error string.

Because Okta brought this user into its staging area (the Import tab) with

Timeout@WorkdayImport.com, Okta now considers this the user's identifier for that specific import event.

Even though HR corrected the data in Workday, Okta's Incremental Imports often fail to fix this because:

1. The corrupted profile is "stuck" in Okta's Import staging area, blocking new updates.
2. Incremental imports look for specific transaction log changes. If Okta doesn't recognize the HR update as a trigger to overwrite the stuck profile, it simply ignores it.

The Recommended Remediation

To get Okta to drop the bad data and pull the clean Workday profile, you need to clear the staging area and force Okta to re-evaluate the entire worker record.

Step 1: Clear the Stuck Import in Okta

Before Okta can pull the correct data, you must delete the corrupted placeholder.

1. In the Okta Admin Console, go to Directory > Directory Integrations > Workday.
2. Navigate to the Import tab.
3. Search for the user (or search for Timeout@WorkdayImport.com).
4. Select the checkbox next to this user and click Clear or Ignore. This removes the corrupted record from Okta's memory.

Step 2: Verify the Workday Business Process

Ensure that the HR corrections are fully committed.

1. Verify that the user's Primary Work Email and Username are correctly populated in Workday.
2. Ensure the "Hire" Business Process is fully marked as Completed (not merely "In Progress" or waiting on a downstream step). Okta often will not pull a profile if the BP is still pending.

Step 3: Run a Full Import

Do not rely on an Incremental Import to fix this. You need Okta to query the entire directory to pull the fresh data.

1. In the Okta Workday Integration, go to the Import tab.
2. Click Import Now.
3. Select Full Import (not Incremental) and let it run.

Step 4: Confirm and Provision

Once the Full Import finishes, check the Import tab again.

1. The user should now appear with their correct Name, Username, and Email.
2. If your Workday integration is set to require manual confirmation for new creations, select the user and click Confirm to provision them into Okta (and subsequently push them to AD/downstream apps).

Best Practices to Prevent This

• Workday Validation Rules: Work with your Workday HRIS team to implement validation rules that physically prevent a "Hire" Business Process from completing if mandatory fields (like Cost Center or standard email formats) are blank.
• Okta Expression Language Fallbacks: Review your Workday-to-Okta profile mappings. If you are using complex Okta Expression Language to build the username/email, ensure you have robust If/Else statements that handle null values gracefully, rather than timing out or failing entirely.

Thank you for reaching out to our Community and have a great day!

--

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