Monitoring and alerts
See every script run, understand statuses and get told when a script fails, stops or slows down.
Google Ads does not tell you when a script quietly stops working. chiliad records the runs of every deployed script and alerts you when something looks wrong.
How runs are tracked
Run data reaches chiliad in two ways:
- The loader reports each run β success or error, duration and the account it ran in. Nothing to set up beyond pasting the loader.
- Google's own execution records are synced through your Google connection.
How far back the history goes depends on your plan: 14 days on Free, 180 days on Solo, 365 days on Studio and above.
A script's execution history
Open a script and choose the History tab. The date range picker above the tabs sets the period.
- 1
Totals for the selected period, including average runtime. A warning appears when runs approach Google's 30-minute limit.
- 2
Where the record came from: Analytics is reported by the loader, Google comes from Google's execution records, Verified is confirmed by both.
- 3
Failed runs show the error message. A count such as 3/5 means the run succeeded in three of five accounts.
Automatic alerts
On paid plans chiliad watches every script for three problems:
- Repeated failures β three failed runs in a row.
- Stopped running β no run for much longer than the script's frequency allows, for example a daily script that has been silent for 36 hours.
- Runtime dropped β runs suddenly finish far faster than usual, which often means the script exits early without doing its work.
Alerts arrive by email, in the app and in Slack. While a problem lasts they repeat at most every few hours. Set a script's Priority to High in its settings to have it flagged as critical.
- 1
The alert names the script and the problem.
- 2
The latest error message, so you often know the cause before opening chiliad.
- 3
View Script opens the script in chiliad.
Notification settings
Each person sets their own notifications in Settings β Notifications, including quiet hours. The Slack webhook is a workspace setting shared by all members.
- 1
Turn individual email notifications on or off.
- 2
The digest summarises script activity daily, weekly or monthly.
- 3
Paste a Slack incoming-webhook URL to send failure alerts to a channel.
Debugging a failing script
- Open the History tab and read the error message of the failed run.
- Check the usual causes: a missing per-account value, a permission the script was never granted (copy the loader again), a renamed campaign or label, or the 30-minute time limit.
- Fix the code or the value in chiliad and save.
- In Google Ads, run a preview of the script to confirm, or wait for the next scheduled run.
Use Logger.log() for extra detail; its output appears in the Google Ads script logs. With the Claude connector you can ask Claude to read the failed run and propose the fix.