WARNING: Your existing scripts might be off the rails

Here’s a pretty common situation in today’s Google Ads Scripts environment: You’ve had a script running smoothly for months or even years. You’ve changed nothing in the script. Yet, at right this moment, the script fails because of “Stopped due to timeout”.

I’ve seen this issue appear in multiple accounts.

The root cause is unknown to me, but it almost certainly has something to do with Google quietly migrating your old scripts to the new environment.

There’s no error in the code. The script just times out.

Here’s the thing: If you do not check your script execution logs, you might not spot this issue and your scripts won’t run!

My current solution: Simply create a completely new script, copy-paste the code from the old script into the new one, and test again.

Most of the time it works without the need for any further debugging.

Happy scripting!

– Nils

PS: If you run into other scripting issues that are a bit more complex, my Google Ads Script Support Call might be just for you. Here’s the link: https://nilsrooijmans.com/google-ads-scripts-support-call/

Author: Nils Rooijmans

Google Ads Performance Architect with a passion for PPC Automation & AI, in particular via Google Ads Scripts.