Update
DV360 and CM360 get threshold alerts — and the timeout that kept them out is fixed
TL;DR
DV360 and CM360 had anomaly detection and scheduled refresh but no threshold alert rules, recorded only as "async report reads — deliberate". Reading the actual cron explained it: rules were evaluated one after another under a single shared time budget with no per-rule timeout, so two slow reports could starve every rule queued behind them.
What shipped
- Threshold alert rules on DV360 and Campaign Manager 360, the same mechanism the other platforms use.
- Every alert fetch is now bounded by its own timeout. A rule that times out is recorded with a named reason and is retried first on the next run rather than disappearing.
- Slow, report-based platforms are evaluated last, so a slow report can only delay other slow reports — not the fast rules behind it.
- YouTube joins anomaly detection, alerts and scheduled refresh as part of the same audit.
The audit that found this could not originally report on YouTube at all — its own platform list was out of date. An audit tool's blind spot is its own vocabulary.
Why fixing the loop was the point
The recorded reason for excluding two platforms was real: their reports genuinely take up to a minute or two to poll. But that hazard belongs to the loop — a hung read on any platform would starve the queue the same way. Bounding each fetch and ordering slow platforms last fixes the mechanism, which is what made the two platforms safe to add rather than an exception to argue about.
Frequently asked questions
- Can I set threshold alerts on DV360 and CM360 now?
- Yes. They use the same alert rules as the other platforms, and the loop that evaluates them now bounds every fetch with its own timeout.
- What happens if an alert rule times out?
- It is recorded with a named reason rather than silently skipped, and because it is the least-recently-evaluated rule it gets retried first on the next run.
- Does a slow platform delay my other alerts?
- No. Report-based platforms that poll slowly are evaluated last, so a slow report can only delay other slow reports.