Differentiate betweeen Cancel and Failure for Deployment Notifications

[wilsonowilson]

How can I differentiate between cancelled and failed builds when setting up build notifications?

I’m trying to set up notifications Netlify sites via webhooks, but I can’t distinguish between the two states.

Very similar issue: Deploy Notifications Cancel vs Failure

[hrishikesh]

This is a known issue:

Status badge incorrectly shows failing when deploy is auto cancelled

Hi there, My site is auto deployed when I make an update to my github repo. I found that whenever I make a change to files which don’t impact the content of my website (e.g. updating the repository .readme) the build is triggered, then cancelled because there was no change to the website content. When that happens the status badge shows as failing, but it’s not failing - it was just automatically cancelled because there was no reason to do the deployment. Is this a bug, or something that I’m…

Slack hook only have option for failed deploy but not cancel

Hi, we recently move to Monorepo and start using Netlify Base directory one of the futures of the Base directory is that if the Base directory doesn’t have changes it will cancel the deploy. we using slack notification but now every time deploy cancel we get failed notification there is way to change this behvier or its still in the works thanks yotav

Don't generate Slack fail notifications for cancelled builds

We have a monorepo that contains the source code for out LAMP based CMS as well as our statically generating public site. When a commit only affects the CMS, we prevent the site from re-deploying with this config in our netlify.toml: ignore = "git diff --quiet HEAD^ HEAD ../library ../netlify.toml ../yarn.lock" This works great. However, our Netlify-powered Slack notification for “Deploy failed” still fires when the build is “cancelled” because of this ignore rule. An option to not fire the…

…and many more

TL;DR, there’s no way at the moment