Why did my Google Ads script stop running?

The usual reasons a scheduled Google Ads script silently stops, and how to find out which one applies.

A scheduled script can stop without anyone being told. Google Ads sends no notification; the script simply has no recent runs, or runs that end in an error nobody reads.

The usual causes

Authorization was lost. The person who authorized the script left, lost access to the account, or had their access revoked. The script cannot run as nobody.
The schedule was removed or changed. Someone edited the script and the frequency was reset, or set to run once.
It fails every time. A renamed campaign, a deleted label, a spreadsheet that no longer exists or a field Google retired makes every run end in an error.
It times out. The account grew and the script no longer finishes within 30 minutes.
It runs but does nothing. A condition stopped matching, so the script exits within seconds and reports success.
The account changed. The account was unlinked from the manager account the script runs in, or was cancelled.

How to check in Google Ads

Open Tools → Bulk actions → Scripts.
Look at the script's frequency and the status of its last runs in the script history.
Open the logs of the last run for the error message.
If it asks for authorization, authorize again with a login that will stay.

How chiliad catches it

Finding out weeks later is the expensive part. chiliad watches every deployed script and alerts you when:

it fails three times in a row,
it stops running — no run for much longer than its expected frequency,
its runtime drops sharply, the sign of a script that exits early.

Set each script's frequency in chiliad to match its schedule in Google Ads so the "stopped running" check knows what to expect. See Monitoring and alerts.

The usual causes

Authorization was lost. The person who authorized the script left, lost access to the account, or had their access revoked. The script cannot run as nobody.

The schedule was removed or changed. Someone edited the script and the frequency was reset, or set to run once.

It fails every time. A renamed campaign, a deleted label, a spreadsheet that no longer exists or a field Google retired makes every run end in an error.

It times out. The account grew and the script no longer finishes within 30 minutes.

It runs but does nothing. A condition stopped matching, so the script exits within seconds and reports success.

The account changed. The account was unlinked from the manager account the script runs in, or was cancelled.

How chiliad catches it

Finding out weeks later is the expensive part. chiliad watches every deployed script and alerts you when:

it fails three times in a row,

it stops running — no run for much longer than its expected frequency,

its runtime drops sharply, the sign of a script that exits early.

Set each script's frequency in chiliad to match its schedule in Google Ads so the "stopped running" check knows what to expect. See Monitoring and alerts.