Hitting an error when logging in. We have a dev store setup with new customer accounts and auth0.
We have been able to login successfully with some email. But one in particular isn’t working. I suspect it may be related to the fact that this email signed up both using a password and passwordless on the auth0 side.
Is there anywhere we can find any logging of the error details?
Request ID: 9d3a1519-5b2e-439a-991f-1a63788cceaa-1746621778
Hey @kalen 
- I think you’re correct here and thanks for sharing the request ID there.
The internal error I’m seeing on our end is referring to a “conflicting user” - so I suspect if the the email is connected to logins on both services it might cause that error to pop up.
Would you be able to see if you can replicate this again with a similar email set up (on both Auth0 and password logins)? If you are and can share another request ID, I can take a closer look and look into this with the team.
Hope to speak soon!
Thanks yes I was able to reproduce it with my email kalenj@gmail.com:
Request ID:
11e55d09-8107-43c3-8791-4cf2df5e0f2c-1746712027
Thanks @kalen - I appreciate you replicating again - we’ll get this looked into. I’ll loop back with you here when I have some next steps 
Hey @kalen - are you still seeing this only on one specific store?
Hey @kalen - we were able to do some digging into this and it looks like the two errors there happened for different but similar reasons.
The older example was the “conflicting user” error message I mentioned - that usually happens when a different identifier for the same email address being used in the request is returned by the third party authenticator. Auth0 might be sending a different identifier for the two different login methods using the same email address, so that aligns with what you mentioned in your initial post. That said, we have also seen this error pop up when merchants are testing out a provider and use the same application credentials on multiple provider records. Currently, this set up is shop-specific on our end, but we are hoping to make it provider-specific (which should resolve the error - can’t guarantee a timeline on this though)
The new example is actually a different error message - this one dealing with auth state. That most commonly happens when an authorization sessions has timed out (over 25 minutes) or when you/the client try to authenticate with the same state param (if a specific state token is used up, any subsequent calls using it will fail).
Hope this makes sense - let me know if I can clarify anything on our end here as always!
Thanks it looks like we need to implement auth0 account linking for these two accounts.
