Weekly Patch - September 6, 2026

#Onboarding/Recruiting

#Signup verification email now sends again when someone asks for a second one

What we fixed: Someone starts signing up on your community's landing page, asks for a verification email, and then doesn't finish. Maybe a spam filter ate the first email, maybe a corporate proxy blocked the page, maybe they just got pulled into a meeting. When they came back and tried the same address again, they saw the same cheerful "check your email" screen, and no email went out. Not that time, not ever. The only way out was a manager or our engineering team clearing the record by hand. We've fixed the check that was causing it. A candidate who never actually joined your community can now request verification again and get it.

See it in action:

1. Sign out and open your community's landing page.
2. Click Create one, enter an email address that has never been used on this community, then click Verify Email. The confirmation screen appears and the email arrives.
3. Don't finish signing up. Come back a few minutes later and submit that same address again.
4. A second verification email arrives. 🎉

Good to know:

• Resending is rate limited so the form can't be pointed at somebody's inbox as a weapon. There's a five minute pause between sends, and a candidate gets three self-service sends before the allowance runs out. That's three messages spread over at least ten minutes, which is room for a real person to recover and not much use to anyone else.
• Running out is not a lock, and it never needs engineering. The allowance restarts three ways: the candidate clicks a link in any verification email they already have, a manager sends them the invitation from the recruitment pool, or a week goes by. Verification links are good for seven days, and sends older than that stop counting, so a spent allowance recovers on its own even if nobody does anything.
• Most candidates who report being stuck aren't. They have a working verification link sitting in their inbox, and following it both signs them up and clears the allowance.
• A verification email that we accepted and then failed to deliver still counts as one of the three. We know that isn't ideal. The alternative is not counting queued email at all, which is exactly the gap an abuse burst would walk through. Nobody stays stuck: it clears on the same seven day clock, and a manager can release the address immediately.
• Everyone submitting on that page now sees the identical confirmation screen, whether the email sent, was paused, was capped, or the address had already joined. That's deliberate. It means nobody can use your signup form to work out which email addresses belong to your members. The tradeoff is that you can't diagnose a stuck candidate by looking at the page, so go to the recruitment pool instead and check that person's last emailed date.

Releasing a stuck candidate: If someone needs a verification email right now, email them from the recruitment pool. Go to Community Management or Project Management > Recruiting, open Moderate candidates on the relevant recruitment, search for their email address, and use the email action on their row to send the invitation to that one person. Their allowance restarts immediately, and they can submit on the landing page again after five minutes.

One catch worth knowing: it has to be a single send to that one person. The bulk email button at the bottom of the pool, the one that goes to everyone matching your filter, does not restart anyone's allowance, because it doesn't record who it reached individually. Sending from the pool never uses up a candidate's own allowance either, so you can send as freely as you like. It can only help them.