# Log in work flow not picking up confirmation email has been confirmed

**URL:** <https://forum.bubble.io/t/log-in-work-flow-not-picking-up-confirmation-email-has-been-confirmed/177845>\
**Category:** Database\
**Created:** [November 11, 2021, 5:19pm UTC](https://forum.bubble.io/t/log-in-work-flow-not-picking-up-confirmation-email-has-been-confirmed/177845 "2021-11-11T17:19:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![airbabble](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@airbabble](https://forum.bubble.io/u/airbabble)\
**Post date:** [November 11, 2021, 5:19pm UTC](https://forum.bubble.io/t/log-in-work-flow-not-picking-up-confirmation-email-has-been-confirmed/177845/1 "2021-11-11T17:19:02Z")

</div>

Hi everyone,

I am hoping someone might be able to help me with this. I have been testing the user on boarding process and have been creating an account, confirming my email, logging out and then logging back in to check the flow.

Unfortunately, my pop up that asks a user who is trying to log in to confirm their email (only meant to appear when “email confirmed is no”) is still appearing, even immediately after I have confirmed the email. Has anyone had this happen before? I will attach some screen grabs in case there are any clues.

 ![image](https://us1.discourse-cdn.com/bubble/original/3X/a/d/ad91b3e4c10eebf08a4a0f13ae559d359ee8b0b4.png)

 ![image](https://us1.discourse-cdn.com/bubble/original/3X/e/6/e67abd26679abe5fa8eb5ad450d712e856965a0a.png)

Thank you!

Clare

---

<div class="post-metadata">

**Author:** ![brenton.strine](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/brenton.strine/32/124156_2.png) [@brenton.strine](https://forum.bubble.io/u/brenton.strine)\
**Post date:** [November 9, 2022, 3:25am UTC](https://forum.bubble.io/t/log-in-work-flow-not-picking-up-confirmation-email-has-been-confirmed/177845/2 "2022-11-09T03:25:52Z")

</div>

I have seen a lot of problems with confirm email. Never solved it. Seems to be broken, or maybe I just haven’t figured it out yet.

---

<div class="post-metadata">

**Author:** ![grace.hong](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/grace.hong/32/109318_2.png) [@grace.hong](https://forum.bubble.io/u/grace.hong)\
**Post date:** [February 28, 2023, 9:21pm UTC](https://forum.bubble.io/t/log-in-work-flow-not-picking-up-confirmation-email-has-been-confirmed/177845/3 "2023-02-28T21:21:14Z")

</div>

Hey all - we recently released a feature that will allow you to customize your email confirmation flow more easily. Learn more here: [Retrieve email confirmation token without sending email](http://forum.bubble.io/t/retrieve-email-confirmation-token-without-sending-email/249367)

---

<div class="post-metadata">

**Author:** ![gabriel18](https://avatars.discourse-cdn.com/v4/letter/g/fbc32d/32.png) [@gabriel18](https://forum.bubble.io/u/gabriel18)\
**Post date:** [March 7, 2023, 2:40pm UTC](https://forum.bubble.io/t/log-in-work-flow-not-picking-up-confirmation-email-has-been-confirmed/177845/5 "2023-03-07T14:40:07Z")

</div>

FYI, I found a solution with some help.

You need to log the user first, check the property “email confirmed” to YES/NO & log out the user if “email confirmed” is NO.  
I added a red text to be hidden when the page loads & only shows after the user is logged out after “email confirmed” has been checked.

It’s seamless if you do the following workflow I did:

 ![Screenshot 2023-03-07 at 15.36.52](https://us1.discourse-cdn.com/bubble/original/3X/1/3/130fdd2934b42511d1b3d209594c6b2ee37bcdac.jpeg)  
 ![Screenshot 2023-03-07 at 15.37.05](https://us1.discourse-cdn.com/bubble/original/3X/e/e/ee5542dd73e4b01fe4321479d46eb450625f1642.png)

More details on this thread:

> [@Retrieve email confirmation token without sending email](http://forum.bubble.io/t/retrieve-email-confirmation-token-without-sending-email/249367/32):
>
> The system won’t know whether or not the user’s email is verified until they log in (because it doesn’t know who the specific user is until they log in). So instead, just immediately log out any user with an unconfirmed email and display an appropriate message. EDIT Alternatively, you could of course simply prevent anyone with an unconfirmed email address from accessing “protected” pages / resources - just depends on the nature of your app and the desired user flow.
