The site-level Notifications page currently offers two deploy events: Deployment started and Deployment completed. Please add a third option: Deployment failed, which fires only when a deployment ends in a failed state.

Expected behaviour: New event option Deployment failed in the Event dropdown on the site Notifications page.

Why: Today, to be alerted about failures we have to subscribe to Deployment completed, which also fires on every successful deploy. On sites that deploy multiple times per day this creates noise, and the failure signal that actually requires action gets lost between routine success notifications. The result is classic alert fatigue: teams either mute the channel entirely or scroll past the one message that mattered.

A dedicated Deployment failed event would let us route only the actionable signal to high-attention channels (on-call email, dedicated Teams/Slack channel, etc.), while keeping the noisy success stream on a low-priority channel, or off entirely.