Automation failed to run - but testing the rule works (Gmail automation)

Hi,

in one of my documents I want to automatically send an e-mail. Whenever I test the rule, it works perfectly. When I press the “send email” button, it works perfectly too.

But for the automation, I always receive the “automation failed to run”. It always says:
"Gmail Send Email failed - Connect to Gmail to use!

Actually the connection should work, because I was able to successfully test the rule…

Any idea why it happens and how I can prevent it?

2 Likes

Hi @Thomas_Meissner - is this still an issue for you? Can you try resetting the connection for gmail and also ensuring you have the right option selected here ( one only works with shared account and the other with private and shared account)

3 Likes

Hi,

thanks for your answer and sorry for my late reply.

I reinstalled the Gmail package. The first day after it still failed. Then it seemed to work until now.

Many thanks and best regards,

Thomas

1 Like

@Thomas_Meissner - glad to hear it is working. Do let us know if you keep seeing it fail every now and then.

I’ve been getting rule failed to run on my gmail back up rule recently. It’s sporadic:

Hi @Ed_Liveikis,

When there are sporadic errors, many times it ends up being a situation where a value is blank for that particular time and causes the automation to throw an error. If you hover over the “Coda Error” tag it might tell you more. Also, you can add a filter for your automation to keep it from running if a certain criteria is met.

Thanks Ben. Hovering over the error shows “Failed to take action in gmail”. Could this be due a blank value? What do you mean by blank value?

The rule in questions is making a PushButtons call on a single button, every day at 9am. The button sends a bunch of emails with either docs or tables, using my email address, and the rule is set to run as my user. Just clarifying the rule works sometimes, fails others.

When something works sporadically, there’s a good chance that the issue is in the data and not the process. This isn’t always the case, but it’s a good place to start.

Let’s say you have a list of emails to send and every email requires a subject in order for Gmail to be able to complete the action. If the push button comes across a row where the subject column is blank, that row will fail and won’t be able to get to the next one. This doesn’t just involve blank values, maybe there’s an email address in there that isn’t a valid email type. It could be any number of things depending on your setup.

For troubleshooting, when it fails, it might help to go through the column and click buttons individually to see if one row in particular throws the error. That helps to narrow down what you might be looking for. If it’s something that can’t be avoided, like maybe there is no email to send that day, you can add a “Disable” rule in the column button so the rows that are affected don’t stop your automation from running all the way through. This way only active buttons get clicked and disabled ones are skipped.