Ability to resend verification email

[GHkrishna]

Steps to Reproduce
Currently when we register as a new user, we are required to verify our email as a prerequisite in order to proceed with the registration flow.

Current behavior
Currently, we are only able to send the verification email once. Which for some reason if is missed/deleted/lost. There is no provision to resent the verification email link.

We get a error when trying to send verification link:

Expected behavior
There should be a resend verifcation link functionality where in we can have a max number of tries. If not maxed out we should be able to resent verification email by displaying something like a resend verification link? displayed

How can this be achieved?

• As per the response updated after adding provision from backend we can handle the display of an additional button accordingly
• As per configuration we should be able resend email for max number of times and throw a contact administrator or max verification link sent error.

[yuvrajraghuvanshi]

Hi @GHkrishna , I'd like to work on it.

[GHkrishna]

Hello yuvraj,
Sure, you can take this up.

However, before we make changes on the frontend, we would want to introduce this feature on the backend. You can see the parent issue
You can start by creating a draft PR

[YogeshK34]

Hi @GHkrishna,

I'd be interested in working on this issue if it's still available.

My proposed approach would be:

1. Add a backend endpoint to handle verification email resends, including retry/rate limits.
2. Update the frontend to show a "Resend verification email" action where appropriate.
3. Make the maximum resend attempts configurable.
4. Add clear error handling and user feedback when limits are reached.

Before I get started, could you let me know if anyone is already working on this? Also, are there any specific requirements, constraints, or implementation preferences I should keep in mind?

Thanks!

[GHkrishna]

I believe there's no one working on this, maybe @RinkalBhojani (or someone on the team) can confirm.

@YogeshK34 I would also suggest a retry cooldown period of some sort before one can try again