As a retailer, we have a lot of employee turnover in our stores, particularly around the Christmas holiday season when we hire a lot of temporary sales associates. And many of these temps return year after year, maybe just to earn some extra cash. When an employee leaves, their AD account is deleted, and their formerly AD-mastered Okta account is converted to an Okta-mastered account and assigned to a special Okta group that gives them access to Workday post-employment, so they can get their paystubs and W-2 forms, etc.

So, this poses a problem if one of these users is hired back. A new AD account is created, and when it imports into Okta, the import stops because the new AD account has the same userprincipalname as their old account (and their Okta username is taken from their AD userprincipalname).

This time of year it's particularly annoying, as I have to repeatedly check my admin dashboard for tasks related to these import conflicts. Then I manually deactivate and delete the user's old Okta account so that the new AD account can be imported and activated.

Does anyone know if it's possible to detect these import errors with an API call? With the right information, I might be able to put together a scheduled task that queries the API for these specific instances, and then automate the deactivation and deletion of the blocking account, and then trigger the completion of the import. The end goal is to eliminate the delay associated with these errors. Thanks!