Proactive updates
A recurring update should send each run. Silence becomes an exception.
6sends in 7 runs
A silent week would be a bug.
Portfolio
Automation Composer
Build an automation. Know when not to send it.
Reports and alerts used to be somebody's morning. This builds one from a rule, shows the exact email or ticket it would send, and holds it if the data is stale.
Two types of automation.
The interesting part of automation is knowing when silence is the right answer.
Exception alerts
It sends only when something qualifies. A quiet week sends nothing.
2sends in 42 checks
A silent week is the correct output.
The Composer - view both types in action.
Proactive updates
Exception alerts
Composer cannot invent a metric. It chooses from Registry, so changing the definition once changes the morning email and the noon dashboard together.
Every value resolves from a governed table. Composer cannot invent a number.
Daily pulse held. The sources aren't ready.
Composerto opsFri 9:00 AM
Leadership did not get the daily pulse this morning.
yesterday_sales_by_locationnot readyLast loaded Tuesday night. The pulse waits until it catches up.