Changing email via the API returns 'The specified new email already exists' when it doesn't

A similar issue has previously been reported but was not resolved. Link.

If I query the user using the email with the API management console no user is returned. So why does the API tell me that it already exists?

1 Like

Any ideas on this one?

So I’ve found out why. I’m using a database connection with auto-migration enabled. Everything you do against that connection; registering, password resets, changing email, will trigger the GetUser request and query your local DB for a user with that email. This means when sending reset passwords for instance, none migrated users will receive an email.

1 Like

Perfect! Glad to hear that and thanks for sharing with the rest of community!

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.