# Delayed Pin for Yahoo Email \*Disclaimer

**URL:** <https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654>\
**Category:** Feature Requests\
**Created:** [August 6, 2020, 4:00pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654 "2020-08-06T16:00:13Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![EatPinellas](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eatpinellas/32/2961_2.png) [@EatPinellas](https://community.glideapps.com/u/EatPinellas)\
**Post date:** [August 6, 2020, 4:00pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/1 "2020-08-06T16:00:13Z")

</div>

@david Is it possible to add a sentence that says something to the effect of certain email platforms take longer than others to receive your pin; after submitting email. I am having users that have Yahoo emails and are waiting 30 minutes for a PIN number. I have had a few people that thought they did something wrong so they keep entering in their email and then get multiple pens half an hour to 45 minutes later.

---

<div class="post-metadata">

**Author:** ![EatPinellas](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eatpinellas/32/2961_2.png) [@EatPinellas](https://community.glideapps.com/u/EatPinellas)\
**Post date:** [August 6, 2020, 4:01pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/2 "2020-08-06T16:01:02Z")

</div>

@david I know that it’s a yahoo issue and not a Glide Apps issue

---

<div class="post-metadata">

**Author:** ![Deena](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/deena/32/9877_2.png) [@Deena](https://community.glideapps.com/u/Deena)\
**Post date:** [August 6, 2020, 4:03pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/3 "2020-08-06T16:03:20Z")

</div>

Another PIN issue thread from today:

[https://community.glideapps.com/t/pin-not-working-too-long/13648/7?u=deena](https://community.glideapps.com/t/pin-not-working-too-long/13648/7)

---

<div class="post-metadata">

**Author:** ![Carlos\_DeSilva](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/carlos_desilva/32/19965_2.png) [@Carlos\_DeSilva](https://community.glideapps.com/u/Carlos_DeSilva)\
**Post date:** [August 6, 2020, 4:04pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/4 "2020-08-06T16:04:38Z")

</div>

Part of it could be that Yahoo, (and some other platforms), may not recognize Glide as a whitelist email. This would cause then to classify them as spam and your users may be searching for an email that would end up in that folder as a result.

---

<div class="post-metadata">

**Author:** ![EatPinellas](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/eatpinellas/32/2961_2.png) [@EatPinellas](https://community.glideapps.com/u/EatPinellas)\
**Post date:** [August 6, 2020, 4:17pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/5 "2020-08-06T16:17:13Z")

</div>

@Deena @Carlos_DeSilva I haven’t had those issues. Updates to the app work perfectly. I have tested with my yahoo and it doesn’t go to spam but just takes forever. I know it’s yahoo issue but if we were able to at least let the customer know that some email platforms take longer it would cut down on pin request and initial frustration before the user is actually able to see how great the apps are. I’m just worried that some customers will be turned off and think that it’s not user-friendly if they’re expecting a pin number to come instantly and it does not

---

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david/32/62831_2.png) [@david](https://community.glideapps.com/u/david)\
**Post date:** [August 6, 2020, 4:17pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/6 "2020-08-06T16:17:17Z")

</div>

No need to mention me directly, I read the forum.

---

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david/32/62831_2.png) [@david](https://community.glideapps.com/u/david)\
**Post date:** [August 6, 2020, 4:17pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/7 "2020-08-06T16:17:53Z")

</div>

Yes, we can look into doing this especially for slow providers like yahoo.

---

<div class="post-metadata">

**Author:** ![Carlos\_DeSilva](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/carlos_desilva/32/19965_2.png) [@Carlos\_DeSilva](https://community.glideapps.com/u/Carlos_DeSilva)\
**Post date:** [August 6, 2020, 4:34pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/8 "2020-08-06T16:34:10Z")

</div>

Well some of us like talking to you directly. You tend to be a straight shooter. 😂

---

<div class="post-metadata">

**Author:** ![Schoodule](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/schoodule/32/12097_2.png) [@Schoodule](https://community.glideapps.com/u/Schoodule)\
**Post date:** [August 24, 2020, 9:54pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/9 "2020-08-24T21:54:51Z")

</div>

Issue with delivering PIN to [gmx.de](http://gmx.de). checked spam, nothing.

I can see user’s email on my user list - but he never went past “provide pin” screen. If I need my user to retry, whats the best way to do it? Shall I delete the row with his email/identifier?

Thx

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [August 24, 2020, 10:08pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/10 "2020-08-24T22:08:11Z")

</div>

They can try to request a new pin.

---

<div class="post-metadata">

**Author:** ![Schoodule](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/schoodule/32/12097_2.png) [@Schoodule](https://community.glideapps.com/u/Schoodule)\
**Post date:** [August 24, 2020, 10:13pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/11 "2020-08-24T22:13:15Z")

</div>

Thanks Jeff, will ask him to retry then. 🤞

---

<div class="post-metadata">

**Author:** ![John\_Burdine\_Jr](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/john_burdine_jr/32/9776_2.png) [@John\_Burdine\_Jr](https://community.glideapps.com/u/John_Burdine_Jr)\
**Post date:** [April 9, 2021, 2:08pm UTC](https://community.glideapps.com/t/delayed-pin-for-yahoo-email-disclaimer/13654/12 "2021-04-09T14:08:21Z")

</div>

I think it would also help if PINs remain active for a few hours, despite new pins being generated. This could slightly increase the likelihood of security problems, but seems small compared to the frustration PINs cause.
