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 doing incorrectly?

Hi, @MeStrak, and welcome to our Netlify community forum.

I completely agree with you that the badge should still show “Success” not “Failed” because there wasn’t a failure.

This issue is a limitation of the status badges which is that, currently, they treat any most recent build that didn’t complete (or isn’t in progress) as a failure.

I have filed an issue to track this. If/when this issue is resolved we’ll update this community topic to let you know.

Thanks for reporting this and please let us know if there are other questions about this.

1 Like

Hi, I have the same issue, which become visible with switching to monorepo. Now when you update one app in monorepo, all other apps’ badges show failed build.

Thanks for that additional data point! I’ve added it to the feature request, and this thread is still the right place to follow to learn when the behavior might change (so far it is not planned, but hoping additional reports like yours will help get the work prioritized!)

Yep, I’m in the same situation. In my case, I’m using Sanity Studio and the Netlify Dashboard Widget. If I push a change that doesn’t affect the website it still triggers a website build and when it’s cancelled, it shows as “Failed” on the badge that is shown in the Sanity Studio…which causes confusion with my client.

Great that you all are already aware, hope you get enough interest to move this up in the priority queue.

1 Like

Hi, @dmorda, and welcome to the Netlify community site. :+1:

That another +1 and I updated the issue to reflect that.