Alerts Only If Necessary

12.6. Alerts Only If Necessary — Alerting Only When It Really Matters

The [SILENT] mechanism — the heart of sustainable automation

This is the most important principle closing out the entire Automation chapter, and it has appeared throughout 17.4 and 18: if there is nothing new or noteworthy, the agent replies with exactly the [SILENT] marker and nothing is sent — avoiding turning the alert channel into noise that gradually gets ignored.

Writing the prompt correctly to avoid the common mistake

Always write it clearly in the form “reply [SILENT] only if nothing changed” — avoid letting this marker get buried inside a long explanatory passage, because the cron mechanism treats any occurrence of [SILENT] in the reply as a signal to suppress sending, even if it is only part of a longer explanatory sentence.

Why this is not just a small technical detail

An automation system that sends a notification on every run even when nothing changed will quickly be trained out of sight by its users — when a genuinely important alert finally arrives, it sinks into the same stream of meaningless notifications that came before it. The principle of deliberate silence is exactly what keeps every alert that does appear genuinely worth reading.

Applied consistently to every kind of job

This principle applies uniformly to every application described in the earlier chapters: KPI reports (17.4) are sent only when the figures are noteworthy, site watching (18.2)/price watching (18.4) only alert when a threshold is crossed, log watching (18.5) only reports serious errors — there is no “send just to be safe” exception for any job type.

Notes

• Always test the [SILENT] prompt by running it with “nothing changed” data before letting the job run automatically — confirm that nothing is actually sent in that case.
• If an alert channel starts receiving notifications too often (several times a day for things that are not truly urgent), treat that as a signal to tighten the “worth noting” threshold in the prompt, not as normal behavior to accept.
• For jobs that combine multiple data sources, make sure [SILENT] is evaluated after everything has been aggregated — avoid the case where one source has a small, insignificant change that still triggers sending a long, unnecessary report.