Zitadel Cloud Email Verification Mail not sent
❌Unsolved🪲Bugs
Hello
We are seeing a problem with hosted Login V2 self-registration:
Problem
During self-registration (register → set password), the UI shows a generic error (e.g. "Could not register user") and the request returns HTTP 500. However, the user is already created in the organization.
The verification email is not sent on the first attempt. If we manually trigger "Resend verification code" in the Console, the email is delivered successfully, so SMTP appears to work.
The user often remains in an inconsistent state (e.g. email unverified, password step seemingly incomplete), and the login/activation flow may ask to set a password again even though one was entered during registration.
Expected
Registration completes in one flow: user created, verification email sent automatically, user can verify and log in.
Environment
- ZITADEL Cloud
- Login V2 required
- Standard ZITADEL SMTP provider enabled
- Local registration allowed on the target organization
Related GitHub issues (possibly same class of bug)
- #12072 — Login V2 generates two email verification codes on registration; first code sent but invalidated
- #11857 — Email verification code sent twice, one invalid
Could you confirm whether this matches a known Login V2 registration defect, which versions contain a fix, and what the recommended workaround is?
Thank you & Best regards
thilo
We are seeing a problem with hosted Login V2 self-registration:
Problem
During self-registration (register → set password), the UI shows a generic error (e.g. "Could not register user") and the request returns HTTP 500. However, the user is already created in the organization.
The verification email is not sent on the first attempt. If we manually trigger "Resend verification code" in the Console, the email is delivered successfully, so SMTP appears to work.
The user often remains in an inconsistent state (e.g. email unverified, password step seemingly incomplete), and the login/activation flow may ask to set a password again even though one was entered during registration.
Expected
Registration completes in one flow: user created, verification email sent automatically, user can verify and log in.
Environment
- ZITADEL Cloud
- Login V2 required
- Standard ZITADEL SMTP provider enabled
- Local registration allowed on the target organization
Related GitHub issues (possibly same class of bug)
- #12072 — Login V2 generates two email verification codes on registration; first code sent but invalidated
- #11857 — Email verification code sent twice, one invalid
Could you confirm whether this matches a known Login V2 registration defect, which versions contain a fix, and what the recommended workaround is?
Thank you & Best regards
thilo
GitHub
Preflight Checklist I could not find a solution in the documentation, the existing issues or discussions I have joined the ZITADEL chat Environment Zitadel Cloud Version v4.13.1 Database CockroachD...
GitHub
Preflight Checklist I could not find a solution in the documentation, the existing issues or discussions I have joined the ZITADEL chat Environment Self-hosted Version 4.12.2 Database PostgreSQL Da...
