I have had the same user need to confirm email multiple times.
What’s strange is that the email is actually confirmed correctly and the user is able to navigate the site. But then later on, the exact same user seems to be flagged as having an unconfirmed email again.
It seems that it happens most when using a new device.
I have heard that cookies are involved with how email confirmation works… but I thought that once an email was confirmed it was permanently marked. But now I am wondering if it actually is just testing that the user has the cookie still. If that’s true, then it would be more accurate to call it “recognized device.”
Do you have any workflow actions that are updating that User’s credentials anywhere? If this happens at any point, and you enable the setting, it will require they reconfirm their email.
This is the only thing I can think of to check. I’ve never heard of Bubble changing a User’s “email confirmed?” back to no without either the User or an admin of the User updating the email address.
This might be a good bug report moment. Curious to learn if you figure out what’s going on!
