Hello,
like you’ve already done quite a bit of digging and setup, so let’s get into what might really be going on here. The message you’re getting:
“Oops!, something went wrong…”
“You may have pressed the back button, refreshed during login…”
is a generic error from Auth0 (or a similar identity provider) that typically happens when:
The session or transaction state (like an SSO token or state param) is no longer valid.
A user hits “Back” and tries to repeat or replay a finished or failed login flow.
There’s an attempt to re-enter the flow without a fresh redirect/initiation.
Use a Clean Redirect to Start Login Again
After rejecting the login due to user-not-found, redirect the user back with something like:
window.location.href = “/login?reason=not_registered”;
Then, on your login page, use that param to show a friendly message and ensure no residual auth state is reused (i.e., don’t just pick up the existing session object if it’s invalid).
- Use clearAppSession or Logout
To completely clear the state after failed auth, you could call:
auth0.logout({
returnTo:
});
This ensures you’re not re-entering the login flow with corrupted or stale auth transaction data.
- Use a Dedicated “Account Not Found” Screen
Rather than sending users back to login, consider redirecting them to a custom screen like:
/account-not-found
Which gives a clear explanation (“Your Google account is not linked to an account here. Please sign up or contact support.”) — and from there, restart the login flow fresh if they try again.
- Debug the Error Page Itself
If you want to suppress the generic “Oops!” message entirely, you’d need to customize the error pages (if using Auth0):
Go to your Tenant Settings → Universal Login → Advanced Options → Error Page
Or in new universal login, handle errors client-side using redirect URLs and query params like error and error_description.
Best Regard,
Kely