# Buggy activation email false alarm?
**URL:** https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004
**Category:** Bug
**Created:** [4월 14, 2017, 7:05오후 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004 "2017-04-14T19:05:38Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@Seth\_Godin](https://meta.discourse.org/u/Seth_Godin)
#### Post date: [4월 14, 2017, 7:05오후 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004/1 "2017-04-14T19:05:38Z")
Hi team.
We’re getting ready to launch (in four days) and as we put our install through its paces, we came across the alert above.
The path was:
Admin in Chrome browser:
• New user created (via csv bulk upload)
• Email invite sent
User (really just the admin testing the process in an incognito browser)
• Email accepted
• Users uses Discourse
• Not actively logged off
• Return to computer next day with incognito turned off
• Log out of admin profile
• Try to log into user profile (not in incognito)
Error occurs.
We see that this sort of false non-activation had been discussed here on the board previously and been declared dead.
> [@Bug in inviting users (?) Cannot login, claiming activation already sent (false)](https://meta.discourse.org/t/bug-in-inviting-users-cannot-login-claiming-activation-already-sent-false/59357):
>
> Just installed from docker the latest 1.8.0.beta7. I think I stumbled upon a bug. Here’s what I did: checked login required in Settings (it’s a closed discussion forum) sent invite to a user user got the invite and clicks the link user got to the page asking for their username and optional password user fills in both fields and clicks “accept invitation” the interface logs them in automatically (no further emails are sent) user logs out user tries to log back in, but now interface says: Yo…
We’re going to try to recreate this in new browsers, no incognito hocus pocus, but since we saw some other bugs (and we’re on the hosted plan, which means we can’t use those solutions) we want to raise our hands early and ask, “is this something real?”
THANKS
Seth and team
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [4월 14, 2017, 9:24오후 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004/2 "2017-04-14T21:24:54Z")
Sure @techapj can have a look, he has worked extensively on the invite system.
What scenarios would cause `no_email_found` to show up here Arpit?
---
### Author:  [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [4월 15, 2017, 5:46오전 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004/3 "2017-04-15T05:46:13Z")
I can reproduce this issue locally, working on a fix now.
---
### Author:  [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [4월 15, 2017, 10:41오전 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004/5 "2017-04-15T10:41:49Z")
Fixed via:
[https://github.com/discourse/discourse/commit/0954367bf42fc09cb40a2bf1b6b5a3776c3d7439](https://github.com/discourse/discourse/commit/0954367bf42fc09cb40a2bf1b6b5a3776c3d7439)
The “redeem invite” code was not consistently sending “Confirm your new account” email if the user has already set password while accepting invite. This was causing error in email log and hence `no_email_found`.
Now invited user will always receive “Confirm your new account” email if they set password while accepting invite. Once they confirm their account the login flow will work perfectly.
@Seth_Godin Thank You for reporting this issue and providing detailed repro steps! 👍
This fix will be deployed on your instance early next week.
---
### Author:  [@Seth\_Godin](https://meta.discourse.org/u/Seth_Godin)
#### Post date: [4월 15, 2017, 12:35오후 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004/6 "2017-04-15T12:35:28Z")
thank _you_ @techAPJ
really appreciate the speedy resolution
I think this is the secret win of Discourse. Nice work @codinghorror
---
### Author:  [@samlmiller](https://meta.discourse.org/u/samlmiller)
#### Post date: [4월 17, 2017, 7:31오후 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004/7 "2017-04-17T19:31:43Z")
Hi @techAPJ ,
We were just doing some testing and we are still encountering the same issue. Can you please give us an update when it should be resolved?
Thanks!
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [4월 17, 2017, 7:35오후 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004/8 "2017-04-17T19:35:47Z")
What version of Discourse are you running (right click and view source)? This was only fixed recently.
---
### Author:  [@samlmiller](https://meta.discourse.org/u/samlmiller)
#### Post date: [4월 17, 2017, 8:08오후 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004/9 "2017-04-17T20:08:45Z")
Hi @jomaxro
We are on a paid hosting plan.
Thanks.
Sam
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [4월 17, 2017, 8:11오후 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004/10 "2017-04-17T20:11:01Z")
> [@samlmiller](#):
>
> Can you please give us an update when it should be resolved?
This is probably going to have to wait 2 to 3 more days till we roll out the change.
We recently added a very sizable feature (user selectable themes) which needs a few days “to cook”, what we are doing now is gradually rolling the change out, but it will probably take a few more days till it hits your instance.
---
### Author:  [@techAPJ](https://meta.discourse.org/u/techAPJ)
#### Post date: [4월 18, 2017, 1:34오전 UTC](https://meta.discourse.org/t/buggy-activation-email-false-alarm/61004/12 "2017-04-18T01:34:51Z")
This topic was automatically closed after 2 days. New replies are no longer allowed.