You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
=======================================
=== PLEASE READ BEFORE FILING ISSUE:
https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendDebugging_8
=======================================
What steps will reproduce the problem?
1. Enable error notification
2. Do not schedule any gmail-delay-send email
3. Wait until an error occurs with delay-send
What is the expected output? What do you see instead?
I expect to be notified only when there's an error with the sending of a
scheduled email for me. If there's a general error with the gmail-delay-send
scripts, but I do not have any scheduled email for delay-send, then I do not
expect to be notified of it, as an end-user.
I get notified for errors even though I do not have any emails scheduled with
delay-send.
What version of the product are you using?
The latest version, where do I check the version? I've provided the most recent
error notification email content.
Please provide any additional information below.
-- Error:Error: Gmail Delay Send failed to connect to one of the Google
Services. This is OK if it happens infrequently, the script will run again in a
few minutes. See here to avoid receiving these notifications:
https://code.google.com/p/gmail-delay-send/wiki/GmailDelaySendOptions_8#Error_No
tifications. Function being called: function () { return
GmailApp.getUserLabels(); } .Error message: Exception: Cannot connect to Gmail
--Stack: at Services (GmailDelaySendWeb):205 (executeCommand) at Services
(GmailDelaySendWeb):27 (cachedExecute) at Services (GmailDelaySendWeb):110
(serviceGetUserLabels) at Utils (GmailDelaySendWeb):209 (userHasLabel) at Utils
(GmailDelaySendWeb):148 (createLabels) at Main (GmailDelaySendWeb):16 (main)
Original issue reported on code.google.com by rah...@gmail.com on 21 Mar 2014 at 5:57
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
rah...@gmail.com
on 21 Mar 2014 at 5:57The text was updated successfully, but these errors were encountered: