Support Forums

How To Auto Cancel Previous Deploy?

Dear All

When I create new deploy (while the previous deploy still processing), I have to wait until the previous deploy process done, or I have to click cancel previous deploy manually. Is there a way to set auto cancel previous deploy? So, the previous processing deploy will be auto canceled if there’s new deploy (like the image below)?

It would be great if canceled deploy is marked as “canceled”, not as “failed” like current.



It sounds like you are asking for a new incoming build to automatically cancel any running builds. If so, there is no way to do so automatically at this time. Would you like me to enter a feature request for this?

If there are many builds scheduled for a single branch, we will build the first and last - skipping intermediate pending builds. New builds do not cancel running builds however.

Regarding the cancelled builds showing as failing, where are you seeing this? My UI shows “cancelled” not “failed” for manually cancelled builds. I see the screenshot, but I cannot find this in our UI. Can you send us a link to where this appears?


Thanks for reply. The screenshot above is from another provider dashboard as reference. By the way, for cancelled is showing cancelled on my dashboard only, but I can’t see it on my badge that I embedded on readme file. So, I only see the success message after the previous failed, not after the cancelled one.

About skipping, is that skipping build will be count as build minutes? Or only the first and last running (as you mentioned above) that count as build minutes?

I don’t have a comment on the first half of your message, but as far as skipped builds are concerned, the answer is no, skipped builds to not count towards build minutes. See more in this thread:

1 Like

Thanks for reference.

1 Like

2 posts were split to a new topic: Automatically cancel on going builds if a new one is pending

Is it already added as feature request? This would be super useful, for example with netlifycms. Thank you


Is the use-case for finishing builds more important than automatically preferring new revisions? Sorry if this is a “it’s just business” decision winky blinky

hey nick, sorry to be slow to reply. can you say a little bit more about what you mean? not sure i am following exactly.

perry, I would like a setting to turn on in which the newest deploy would cancel current builds (on the same project)

thanks! Is the hope that this would make it so that you could stop a current deploy by pushing another change, for example if you realized you had made a mistake?

1 Like

I have to stop it manually but every time I push I want the latest to build

Hi @NickCarducci,

This is how we have it currently:

Does that not work for you?

If you want the current one that’s building to immediately cancel, we currently do not do that. But yes, we could take that as a feature request.

hrishikesh, 1) please take this as a feature request. While I’m here, I’ll #Feature request 2) email notifications for build failures as well

Hi @NickCarducci,

Thank you for pointing out how you expect the feature to work. We’d pass it on to the developers and update the thread if anything changes.