Setting alertEscalationPolicy on a group silently drops its alert channels

Checkly's CheckGroupV2 reference does document the mechanism, and I had not found it when I hit this: "If you want the group's alert settings to override check-level alert settings, you must set the alertEscalationPolicy. Otherwise, the alert settings of individual checks will be used, even if alertChannels is defined in your group."

So this is not an undocumented behavior. Two narrower things are still true, and I think they are the actionable ones.

The warning is written for a reader who WANTS the override. I set alertEscalationPolicy to get repeat notifications for a single-channel setup, and the override arrived as a side effect - so the sentence that would have saved me is addressed to someone with the opposite intent, and reads as not applying.

And the dangerous state is documented nowhere: nothing on the page says what happens when alertEscalationPolicy is set and alertChannels is not. The docs explain how to obtain the override. Nothing explains standing in it having named no channel, which is the only configuration here that silences checks.

Requests unchanged in substance, reordered by what would have helped:

1. Warn at deploy time when a group has an escalation policy and no alert channels while its members carry direct subscriptions. Documentation cannot reach someone who does not know to look.

2. Say it in the parameter description for alertEscalationPolicy itself, framed as a consequence rather than as an instruction for the reader who wants it.

3. Render it in the dashboard. A group that overrides alerting and names no channel should not look identical to one that alerts normally.