Email from Google -- UrlFetchApp error

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install the scripts
2. Compose an email
3. Run
4. Compose some more
5. wait

What is the expected output? What do you see instead?
The emails composed in 4. are ignored instead of being processed

Original issue reported on code.google.com by ld2...@g.rit.edu on 9 May 2013 at 11:05

[GoogleCodeExporter]

I had a "similar" issue. I went in and turned on for notifications when it 
fails and discovered that when it tries to run automatically every 5 min. it 
sends this message:

Attempted to execute command: function () { return 
UrlFetchApp.fetch(urlString); } 5 times without success. Error message: 
Exception: Unexpected error: 
http://gmail-delay-send.googlecode.com/files/0.7.6.combined. Aborting :-( (line 
378, file "runGmailDelaySend")


However, if I manually run the script it works just fine. 

Original comment by cac3...@g.rit.edu on 10 May 2013 at 4:00

[GoogleCodeExporter]

I have the same issue

Original comment by nech...@gmail.com on 10 May 2013 at 9:50

[GoogleCodeExporter]

Today, Google sent me an email with all the errors that have caused this. It 
actually attempted to run, but crashed every time.

Original comment by lev.dol...@gmail.com on 10 May 2013 at 10:54

Attachments:

• errors.html

[GoogleCodeExporter]

Thanks for reporting the errors guys.

Nothing has changed with the code or the file that's hosted at 
http://gmail-delay-send.googlecode.com/files/0.7.6.combined for a while so I'm 
not sure how best to debug.

Is everybody that's seeing the error a new users (eg. installed maybe in the 
last week?).

(After signing into your google account) Able to access the url: 
http://gmail-delay-send.googlecode.com/files/0.7.6.combined and have a file 
downloaded?

-Blair

Original comment by blairk...@gmail.com on 10 May 2013 at 7:18

• Changed state: Accepted

[GoogleCodeExporter]

Issue 61 has been merged into this issue.

Original comment by blairk...@gmail.com on 10 May 2013 at 7:18

[GoogleCodeExporter]

The script is downloaded instantly, no problems.

Original comment by lev.dol...@gmail.com on 10 May 2013 at 7:37

[GoogleCodeExporter]

Hey lev.dolgov,

(Sorry for all these steps, but I can't reproduce this w/ my account)

Do you think you could try un-installing the triggers and try setting them up 
again?

Instructions for un-installing triggers:
https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendUninstall
(don't do the last step of deleting the spreadsheet).


Instructions for installing them again:
https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendInstall#[_]_Manual
ly_Setting_trigger

Original comment by blairk...@gmail.com on 10 May 2013 at 7:42

[GoogleCodeExporter]

I am an old user (two accounts) and is seeing the same errors... I have also 
tried setting the triggers to 15 and then 30 min but still the same error

Original comment by jake.le...@gmail.com on 11 May 2013 at 12:42

[GoogleCodeExporter]

Issue 62 has been merged into this issue.

Original comment by blairk...@gmail.com on 11 May 2013 at 1:35

[GoogleCodeExporter]

Original comment by blairk...@gmail.com on 11 May 2013 at 1:36

• Changed title: Email from Google -- UrlFetchApp error

[GoogleCodeExporter]

Hey Everybody,

Other google apps users are experiencing the same error.  Looks like it was 
caused by a new version of Google Apps Scripts being releases with some 
non-backwards compatible changes.

There are two bugs to track this : 
https://code.google.com/p/google-apps-script-issues/issues/detail?id=2738 and 
https://code.google.com/p/google-apps-script-issues/issues/detail?id=2740.

You can 'star' this bug report to receive notifications of when any new 
information / fix is released.

Sorry for the inconvenience!

-Blair

Original comment by blairk...@gmail.com on 11 May 2013 at 1:40

[GoogleCodeExporter]

Hi Blair,

I am not a new user of Delay Send. It has been installed for a couple of months 
but I have not used it in about a month. I have already been in email contact 
with you about these long error emails I keep getting. What is the best 
solution for now?  To uninstall Delay Send?

Thanks,
Panther

Original comment by pantherc...@gmail.com on 13 May 2013 at 3:08

[GoogleCodeExporter]

Same issue here. Old user. Tried reinstall. 

Any updates?

Original comment by sabin.po...@gmail.com on 13 May 2013 at 11:14

[GoogleCodeExporter]

pantherchick and sabin.popescu,

I'm working on a new version of the script which removes the dependency on 
UrlFetchApp, but it probably won't be ready for a few more days.

If you would like to stop receiving the emails from Google there are two 
options:
  1.) One is to remove the triggers from the script. You can do so by following the steps here: https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendUninstall but omitting the final step which removes the spreadsheet altogether.
  2.) The second option is to uninstall completely. (instructions are on the same link).

I would actually recommend you un-install completely and just wait a bit for 
the new version to be released. I'll probably send an email to the google group 
(https://groups.google.com/forum/?fromgroups#!forum/gmaildelaysend) to have 
them try out the version first, so join if you would like to be part of that 
group.

Otherwise we just have to wait for a fix to be released by the Google Apps 
Script team.

Again, sorry for the inconvenience, working to get this all fixed up!
-Blair

Original comment by blairk...@gmail.com on 13 May 2013 at 1:21

[GoogleCodeExporter]

Thanks for the updates and working to fix the error Blair! :)

Original comment by d7e7r7 on 13 May 2013 at 2:32

[GoogleCodeExporter]

Blair -
   Are there any limitations on the DELAY_SEND? 
Dee

Original comment by dee.corb...@maryland.gov on 13 May 2013 at 4:32

[GoogleCodeExporter]

Unless google made another update to urlfetchapp at the same time I implemented 
my workaround today, the workaround that I'm using that seems to be working so 
far is this:

1.  Download the 0.7.6.combined script 
(http://gmail-delay-send.googlecode.com/files/0.7.6.combined).

2.  In your gmail delay spreadsheet, add a new script file to the project so 
there would be now three scripts.  Replace the default content of the third 
script with the contents from the 0.7.6.combined.

3.  In the delay email script, change the value for "RUN_LOCAL_VERSION" to true.

So far it seems to be working.  The email I've delayed sent to 1:53pm (today) 
but created at 1:50 was successfully sent.  That was my third test email sent.

Original comment by roscoe.s...@maryland.gov on 14 May 2013 at 5:56

[GoogleCodeExporter]

It works!
Email created at 7:21 p.m. was sent at 7:30 p.m. (local time) it was to be
sent at 7:26, so the script runed at 7:30, it's working just fine!
Thanks a lot! (I send a mail everynight at 0:00 to a googlegroup, they were
asking me why it wasn't being sent at that time... it's not easy to do that
allways manually - you've just saved my day (and lots of nights)!
Helena

Original comment by helena.a...@gmail.com on 14 May 2013 at 6:38

[GoogleCodeExporter]

I also agree, Roscoe's fix, 
https://code.google.com/p/gmail-delay-send/issues/detail?id=60#c17, works like 
a charm.

Original comment by krkee...@gmail.com on 14 May 2013 at 8:43

[GoogleCodeExporter]

I cannot download the 0.7.6.combined script, mentioned above #17, #18 & #19 
(see attached).  Has this version been released? 

Original comment by dee.corb...@maryland.gov on 14 May 2013 at 9:44

Attachments:

• [Delay Send 0.7.6.combined.docx](https://storage.googleapis.com/google-code-attachments/gmail-delay-send/issue-60/comment-20/Delay Send 0.7.6.combined.docx)

[GoogleCodeExporter]

The error message in your attachments means that you had downloaded the 
document.  

You are not supposed to open the document using adobe acrobat.  It is a text 
file with the name "0.7.6.combined".  Use notepad or wordpad or Word to open it 
up and then copy the contents as noted above.

Original comment by roscoe.s...@maryland.gov on 14 May 2013 at 9:51

[GoogleCodeExporter]

Thank you I will ask our technical contractor to take a look. 

Original comment by dee.corb...@maryland.gov on 14 May 2013 at 10:07

[GoogleCodeExporter]

Now with the new script works just fine.
Thanks for all the work and quick fix.

Original comment by lbarreir...@gmail.com on 14 May 2013 at 10:12

[GoogleCodeExporter]

what do we name the '3rd script' that we copy into the script editor? I've got 
'runGmailDelaySend.gs' , 'date.gs' , and then then '3rd' I don't know what to 
name (I just called it 'GmailDelaySend.gs' at the moment

sorry if this is a silly question

Original comment by eladouc...@demandforce.com on 14 May 2013 at 11:11

[GoogleCodeExporter]

I named it     0.7.6.combined
And worked just fine!

Original comment by helena.a...@gmail.com on 14 May 2013 at 11:16

[GoogleCodeExporter]

The actual script name can be anything you want.  I used "0.7.6.combined" as 
the name of the script to remind me of the version.

Original comment by roscoe.s...@maryland.gov on 14 May 2013 at 11:17

[GoogleCodeExporter]

The issue for two other scripts noted in comment #11 were fixed earlier today.  
So perhaps the workaround for this script is no longer needed as well.

Original comment by roscoe.s...@maryland.gov on 15 May 2013 at 6:21

[GoogleCodeExporter]

@roscoe.s

would there be a problem if I keep this combined work around on? thanks

Original comment by nickande...@gmail.com on 15 May 2013 at 11:43

[GoogleCodeExporter]

I'm still running the workaround.  I'm following the "if it ain't broke, don't 
fix it" rule.  Usually, workarounds become the new bug when the original 
problem gets fixed.  That's why it is usually better to have an actual fix then 
use a workaround.  In this case, it seems to be running okay.  

I'll probably disable the workaround later today out of curiosity to see if the 
original problem was actually fixed.

Original comment by roscoe.s...@maryland.gov on 16 May 2013 at 12:08

[GoogleCodeExporter]

Disabled workaround.  I still received error so it looks like the original 
problem has not been fixed.

Original comment by roscoe.s...@maryland.gov on 16 May 2013 at 12:31

[GoogleCodeExporter]

I never used the workaround, and the code is still broken for me. Should I
switch to the workaround now?

-- 
*

Warm regards,


Joel Gross

joel@coalitiontechnologies.com

www.coalitiontechnologies.com

p: 323-545-4778

f: 1-888-783-3618



�We are what we repeatedly do. Excellence, therefore, is not an act but a
habit�.

CONFIDENTIALITY NOTE:  This electronic message transmission and any
attachments contains information from Coalition Technologies which may be
confidential or privileged. The information is intended to be for the use
of the individual or entity named above. If you are not the intended
recipient, please immediately delete this e-mail and be aware that any
disclosure, copying, distribution or use of the contents of this
information is prohibited.  If you are the intended recipient, consider
this information to be confidential unless otherwise noted.

*

Original comment by j...@coalitiontechnologies.com on 16 May 2013 at 3:32

[GoogleCodeExporter]

the work around is working fine for me... tried to disabled it and the "fix" 
didn't work... unless somebody reports that the fix is already working or a new 
version is released that works well... i'm sticking to this work around thing...

Original comment by povida.l...@gmail.com on 16 May 2013 at 11:50

[GoogleCodeExporter]

Hello everybody,

The new version that I mentioned before is taking longer than I thought to 
rollout. Using the workaround above (thanks again Roscoe!), I created a new 
version of Gmail Delay Send and posted it to the install page.

If you haven't performed the workaround above and are having difficulty then 
please follow the un-install instructions here: 
https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendUninstall

Then install the script again 
here:https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendInstall#Optio
n_1_-_Copy_existing_google_doc_(less_technical)

Again, sorry for the inconvenience!
-Blair

Original comment by blairk...@gmail.com on 18 May 2013 at 1:31

• Changed state: Fixed

[GoogleCodeExporter]

The workaround works for me too. And not without the workaround. Obviously 
Google hasn't fixed the problem on their side.

I didn't try the new version, I found it easier to apply the workaround.

Original comment by marlar...@gmail.com on 21 May 2013 at 8:12

[GoogleCodeExporter]

Roscoe, could you explain the idea behind your fix? What does it do?

Original comment by marlar...@gmail.com on 21 May 2013 at 8:24

[GoogleCodeExporter]

Originally, the actual code -- called the "third script" for reference -- that 
does the "heavy work" to delay send emails is actually taken from this site: 
http://gmail-delay-send.googlecode.com/files/0.7.6.combined

So when delay-send runs, it grabs the "third script" from that site and runs it.

The change that Google made broke delay-sends ability to grab the third script. 


Thus, the first goal is to get the third script since delay-send can't get it.  
The second goal is to have delay-send run the local copy rather than grab it 
from the site.

The workaround has you copy the third script from that site and add it to the 
project that has the other two scripts that you had already copy-and-pasted.  
So the first goal is achieved.

Then you change a variable RUN_LOCAL_VERSION to tell delay-send to run the 
third script that you added rather than try to grab the script from the 
website. The second goal is achieved.

The obvious drawback to this is that whenever there is an update to the "third 
script", you will have to manually copy and paste that update since it will no 
longer grab anything from the site.

Original comment by roscoe.s...@maryland.gov on 21 May 2013 at 12:26

[GoogleCodeExporter]

Roscoe, thanks for your fix and the explanation of the idea behind it. It makes 
sense. :)

Original comment by marlar...@gmail.com on 21 May 2013 at 12:30

[GoogleCodeExporter]

Issue 40 has been merged into this issue.

Original comment by blairk...@gmail.com on 24 May 2013 at 7:49

[GoogleCodeExporter]

Issue 61 has been merged into this issue.

Original comment by blairk...@gmail.com on 31 May 2013 at 11:29

[GoogleCodeExporter]

Issue 71 has been merged into this issue.

Original comment by blairk...@gmail.com on 13 Jun 2013 at 12:15

[GoogleCodeExporter]

Issue 72 has been merged into this issue.

Original comment by blairk...@gmail.com on 13 Jun 2013 at 12:18

[GoogleCodeExporter]

Issue 75 has been merged into this issue.

Original comment by blairk...@gmail.com on 19 Jun 2013 at 4:50

[GoogleCodeExporter]

looks like it's fixed!

Original comment by chetmies...@gmail.com on 19 Jun 2013 at 5:32

[GoogleCodeExporter]

Ok, I think I've missed a vital step somewhere... doesn't seem to work.

Installed, changed time zone, didn't work (items stayed in draft).

Downloaded workaround code, copied to new script file, realized that it was 
already done when I went to change the "local" value to true... it was already 
true. Then started comparing one of the existing script files to the one I 
downloaded, which appeared the same. So deleted my newly put in script file. 

Closed everything, reopened, no love. Items still sitting in "draft". 

What key element am I missing? 

Original comment by germaine...@gmail.com on 4 Jul 2013 at 6:43