Auth0 Universal Login displays unknownErrorDescription instead of alreadyVerifiedDescription when clicking an email verification link for the second time

Get Help
1

Hi Auth0 Community,

We are using Auth0 for authentication and have implemented the email verification flow during user registration.

Our expected behaviour is as follows:

  1. When a user registers with their email address, Auth0 sends an email containing a verification link.

  2. When the user clicks the link for the first time, the email is successfully verified, and the success message is displayed.

  3. If the user clicks the same verification link again, we expect Auth0 to display the message configured in the alreadyVerifiedDescription field, indicating that the email address has already been verified.

Current Issue:

When the user clicks the same verification link for the second time, Auth0 displays the message configured in unknownErrorDescription instead of alreadyVerifiedDescription.

We have already configured the following text under:

Auth0 Dashboard → Branding → Universal Login → Edit Text and Translations → Email Verification Prompt

  • alreadyVerifiedDescription – Configured with a message indicating that the email address is already verified.

  • unknownErrorDescription – Configured with a generic error message.

However, the unknownErrorDescription message is consistently displayed when the same verification link is reused.

Expected Behaviour:

We would expect Auth0 to identify that the email address has already been verified and display the corresponding alreadyVerifiedDescription message rather than the generic error message.

Questions:

  1. Is this the expected behaviour of Auth0, or is there any configuration missing in our Universal Login setup?

  2. Under what circumstances is the alreadyVerifiedDescription field triggered?

  3. Is there any way to configure Auth0 to display a specific message when a user clicks an already-used verification link, rather than displaying the generic unknownErrorDescription?

  4. If this is the intended behaviour, is there any recommended workaround to provide users with a more meaningful message?

Any guidance or suggestions would be appreciated.

Thank you!