Open since 2020 and still no resolution? This false negative signal prevents us from marketing netlify on our project pages.
Sadly there has not been enough movement on this issue.
Just went down this rabbit hole before finding this thread.
In my case, it’s triggering ‘deploy-failed’ email / slack notifications on no-content-change, which directly impacts our engineers that monitor for real/actual build problems.
Please add my +1 (or +5 for all the people here that have to deal with false negatives…/false positive alerts)
1 Like
Hey there, @danielthedifficult 
Thanks so much for following up here. I have shared your feedback directly with the Product team!
Same issue, I had to remove the Netlify badge as a consequence.
Thank you for letting us know.
+1, I spent hours trying to figure out what I was doing wrong
Hi @trevoruptain 
thank you for letting me know!
Just gonna throw my name in the “using a monorepo and this is breaking our errors system” bin.
+1, This causes a lot of noise in our system and it would be good to show failing on real failures instead of ignored builds.
Good news, everybody! We have just (1 hour ago I believe) deployed the change that should cause canceled deploys to no longer report as failing!
Can anyone confirm the change on a previously-problematic site for us?
Please see followup below with a correction/redaction.
2 Likes
Unfortunately, I was mistaken in my last post, about the fix and many people in this thread likely would not have experienced an improvement at least in the badge situation. Very sorry to misinform! We’ll follow up again once the work is completed around the badges!
1 Like
UPDATE: The fix for this has been really released now. Let us know how it goes for all of you.
1 Like
Failed during stage ‘checking build content for changes’: Canceled build due to no content change
Slack notifications are still being sent with a “failed” status even though the build was just “skipped”.
Thank you for flagging it. We’ve passed it to the team.
Hey @tsdorsey,
Could you share a screenshot along with the deploy ID so we can check this?
Thank you for sharing, we’ve relayed it back to the devs.
Hi @hrishikesh,
Is there any further update on Slack notifications still being marked as failed?
Hi, unfortunately there is no update on this feature request. 
it’s in the queue but we have no specific updates.
I saw the announcement that Netlify had an official Slack app. 
Thank heavens I thought, I’m sure a first class app will have first class support for canceled builds. I installed it, configured most notices to go to our logging channel and then directed just two statuses (Errored and Previously successful deploy failed) to the #errors channel.
It still notifies the errors channel about cancelled builds!!!
Aaaaaaaaaaaaarrrrrgggghhhhhh!
We have been requesting this feature for nearly four years.
The first instance I found was January of 2020. We get it, things come up. We’re pretty much all devs here. But this is getting ridiculous.
I’m not here to put you down or call you names. I truly understand how this can happen. I’m here to let you know that more than a new Slack app, more than new team member types, more than another framework with native netlify support, more than expanded environment variable configurations, the thing that would increase my quality of life as a customer is to not be falsely notified that a build has failed.