User imports are being run from an application into Okta. On the Imports tab, however, a significant number of users are displaying the following error, even when no conflict is present.

This choice creates a conflict.

This does not seem correct, as many of these users do not yet exist in Okta.

• Okta Expression Language (OEL)
• Provisioning-Enabled Application with Imports into Okta
• Custom "Okta username format" Configured on the Provisioning > To Okta Tab
• Okta Classic Engine
• Okta Identity Engine (OIE)

This error occurs because the incoming user’s unique identifier (username or email) is either already claimed by an existing record, frequently a deactivated account, or the custom Okta expression used for the Okta username format under Provisioning > To Okta is incorrect.

For example, the expression may be malformed or make reference to an AppUser profile that does not yet exist, such as okta_org2org.userName. As this expression cannot be properly evaluated, a large number of users on the Import tab are displayed with the error.

Follow the steps below to resolve the issue:

1. Resolve Attribute Collisions (Data Conflicts): Search the Okta Directory to ensure the incoming user's unique identifier (username or email) is not already claimed by an existing record.
   1. Navigate to Directory > People and search for the specific username or email.
      • NOTE: Ensure the filter is set to include users with a Deactivated status.
   2. If a match is found (Active or Deactivated), either delete the conflicting account or edit its profile to change the email/username, thereby "freeing up" the attribute for the new import.

2. Review the OEL Expression Being Used for the Okta Username Format for Any Errors:
   1. If there are any direct references to the application variable name (such as okta_org2org.userName), change this to refer directly to the AppUser profile, such as appuser.userName.
      • Direct references to the application variable name will fail because the user's AppUser profile does not yet exist.
   2. Once the OEL expression is modified, preview it with an existing user to ensure it is properly evaluated and error-free.
      • NOTE: It is important to thoroughly test any new or modified OEL expressions in an Okta Preview or non-production environment to avoid any potential issues.