• Workday
• Incremental Import

Incremental imports are designed to fetch data for workers identified as having updates since the last incremental import. However, these updates must pertain to certain attributes, such as base attributes and non-effective future-dated custom attributes. Changes to effective-dated custom attributes alone do not trigger an incremental import.

In simpler terms, if there are no changes to base attributes, non-future, or future effective dated custom attributes on the Workday side, an incremental import will not bring the user data into Okta or link them appropriately.

Please note that when users have Workday as their source, the standard procedure involves deactivating them within Workday first. Following this, a full import operation should be executed, resulting in the deactivation of these users within Okta as well. It is important to note that manually unassigning Workday-sourced users in Okta is not the recommended approach.

1. Ensure that they are configured correctly and aligned with the specific use case. Verify that the mapping between Workday and Okta is accurately defined.
2. When users need to be linked or relinked, consider running a full import rather than an incremental one. A full import synchronizes all users, ensuring that their profiles are correctly matched.
3. Set up scheduled full imports at regular intervals to catch any changes or updates in Workday. This proactive approach ensures that the user data remains synchronized without manual intervention.