Okta Fails to Import Workday Users After Disconnection
Last Updated:
Overview
Okta fails to import users from Workday after a disconnection because the disconnection masks the user in Workday. Resolve this issue by temporarily updating the affected user profile in Workday to make the user visible to the import process. When a user disconnects from the Workday integration, subsequent imports fail to detect and import the user into Okta.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Workday
- Imports
- User Administration
Cause
Disconnecting a user from Workday masks the user on the Workday end. This masking prevents the Workday integration import from detecting the user within the application.
Solution
How is the Workday user import issue resolved?
Resolve the import issue by temporarily updating the affected user profile in Workday and running the import again.
- Update the affected user profile in Workday temporarily by adding an extra letter or digit to an attribute, such as the first name or last name.
- Run the Workday import in Okta again.
NOTE: If the import still fails to bring over the user, open a support ticket with Okta Support for additional assistance.
