PierreGode / gmail-delay-send

Automatically exported from code.google.com/p/gmail-delay-send
0 stars 0 forks source link

Emails sends 5 minutes later no matter what #155

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
=======================================
=== PLEASE READ BEFORE FILING ISSUE:
https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendDebugging_8
=======================================

What steps will reproduce the problem?
1.I set email time @10:15 (15 minutes after current time)
2.Email sends at 10:00 instead

What is the expected output? What do you see instead?
Expected that the email would send at 10:15, instead the email sends early

What version of the product are you using?
newest one

Please provide any additional information below.
I followed the instructional video and the written instructions. 

Original issue reported on code.google.com by ali.bere...@gmail.com on 13 May 2014 at 3:09

GoogleCodeExporter commented 9 years ago
Hello Ali,

Strange problem!

Could you try something like "@+15 minutes" to see if that works as you had 
intended?

Also you can check when Gmail Delay Send thinks the message should be sent 
here: 
https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendOptions_8#Test_a_d
ate_or_time

Original comment by blairk...@gmail.com on 2 Jun 2014 at 3:58

GoogleCodeExporter commented 9 years ago
I've notice that it can handle the @+4 minutes , but it can't do @8:30am. 
if it's set to @8:30am, it'll just send it as soon as the script runs. I 
haven't tried other variations yet, but this is definitely the case.

I did the same exact step at the OP and same results. but when i do it by 
applying +Xminutes, it follows the parse.

Original comment by mikep...@gmail.com on 25 Jun 2014 at 3:14

GoogleCodeExporter commented 9 years ago
Hey guys,

And just to verify, does using the 'testing a data or time' return the result 
that you would have expected?

https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendOptions_8#Test_a_d
ate_or_time

Original comment by blairk...@gmail.com on 27 Jun 2014 at 3:06

GoogleCodeExporter commented 9 years ago
I've tried multiple dates in the "testing a date or time" and it won't parse 
any of them.

Original comment by miss.twi...@gmail.com on 6 Sep 2014 at 9:15

GoogleCodeExporter commented 9 years ago
Hello,

Performing a bug-scrub. Is this bug still valid? If so, please re-open  :-)

Thanks!
-Blair

Original comment by blairk...@gmail.com on 15 Dec 2014 at 11:21

GoogleCodeExporter commented 9 years ago
I have no idea. I no longer need the ability to send a delayed email. I could 
never figure out how this works.

Original comment by ali.bere...@gmail.com on 16 Dec 2014 at 2:04

GoogleCodeExporter commented 9 years ago
I am still having this same exact issue as of today, so it does not appear to 
be fixed

Original comment by Drewalln...@gmail.com on 8 Jan 2015 at 1:37

GoogleCodeExporter commented 9 years ago
Hello DrewallnJohnson,

I would love to help figure our the issue, but I need some information as to 
what you're trying and whats going wrong.

Could you try to follow these steps to debug?

https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendDebugging_8

Original comment by blairk...@gmail.com on 9 Jan 2015 at 1:43

GoogleCodeExporter commented 9 years ago
Yes, I tried those steps, but no luck. Basically, the issue is as described 
above--certain scripts do not work, in the sense that they send as soon as the 
next cycle runs (i.e. every 5 minutes). Specifically, scripts such as 
@1/14/2015 8:30am and @8:30am do not work, but scripts such as @+17 minutes and 
@+5 hours DO work. Note that I have also tried all the scripts I have used in 
gmail at the Datejs website, and they parse the script no problem; it is only 
when I actually go to use it is there an issue.  

Original comment by Drewalln...@gmail.com on 14 Jan 2015 at 8:03

GoogleCodeExporter commented 9 years ago
DrewallnJohnson,

Thanks for the feedback. Note that a date such as @8:30 doesn't take the 
current day into account (a known datejs bug). So if it's currently 2pm and you 
enter @8:30am it will assume that you meant earlier that morning and send 
immediately.

The other date you mentioned though ('1/14/2015 8:30am') should work fine. If 
you do have time, could you follow the debug steps mentioned before w/ a date 
formatted like that?

Thanks,
-Blair

Original comment by blairk...@gmail.com on 14 Jan 2015 at 1:21

GoogleCodeExporter commented 9 years ago
Blair,

Thank you for the quick responses!! I have followed the debug steps using a 
date formatted as discussed -- and I received a lengthy email with the debug 
logs. Shall I copy and paste it here in the forum, or is there an address to 
which I should forward it?

Thanks, 

Drew

Original comment by Drewalln...@gmail.com on 16 Jan 2015 at 9:20