How to read a Google Ads script's execution history

The History tab of a script in chiliad lists its runs for the selected date range. Reading it well tells you in a minute whether a script is healthy.

The summary

• Total executions — how many runs were recorded in the period. Compare with what the schedule should produce: a daily script over 30 days should show about 30.
• Success rate — the share of runs without an error.
• Last run — when the script last ran anywhere.
• Average runtime — with the maximum, and a warning when runs approach the 30-minute limit.

Status

• Success — the run completed.
• Error — the run threw an error; the message column says which.
• A count such as 3/5 — a manager-level run that succeeded in three of five accounts.

Source

• Analytics — reported by the chiliad loader at the end of the run.
• Google — taken from Google's own execution records, synced through your Google connection.
• Verified — the same run seen in both.

Accounts, duration and date

Each row shows the customer ID the run happened in, or the number of accounts for a manager-level run, how long it took, and when.

What to look for

• Gaps. Missing days mean the script did not run at all.
• The same account failing. Usually a missing value or an account-specific problem, not the code.
• Sudden short runs. A script that used to take a minute and now takes two seconds is probably exiting early.
• Runtime trending upward. Deal with it before it reaches the limit.

How far back you can look depends on your plan: 14 days on Free, 180 on Solo, 365 on Studio and above.