Okta Application Profile Push Fails to Apply Updates for Some Users
Last Updated:
Overview
An application profile push fails to apply updates for some users because the initial mapping distribution was skipped. Resolve this issue by saving the mappings again and applying the updates to all scoped users.
Review the following image for an example of the warning message displayed when updates are not applied.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Profile Editor
- Applications with provisioning
- User Lifecycle Management
Cause
The administrator skipped the initial broad application of the mappings following a change by selecting the Don't apply updates option.
Review the following image for an example of the Don't apply updates option.
Solution
How are skipped profile mapping updates applied to all users?
Trigger the broad distribution of the mappings to all scoped users by saving the mappings again in the Profile Editor.
- Navigate to Directory > Profile Editor in the Okta Admin Console.
- Select the target application.
- Click Mappings.
- Click Save Mappings.
- Select the Apply updates now option to distribute the updates to all users scoped by the application.
Review the following image for an example of the Save Mappings button.
NOTE: This action pushes all attributes of the assigned users to the application, rather than pushing only a specific attribute.
