# The pipeline delay blocks are not cancelled **URL:** \ **Category:** Ignition\ **Created:** [September 25, 2026, 10:25am UTC](https://forum.inductiveautomation.com/t/the-pipeline-delay-blocks-are-not-cancelled/117187 "2026-09-25T10:25:53Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![CP5\_Informatica](https://avatars.discourse-cdn.com/v4/letter/c/f04885/32.png) [@CP5\_Informatica](https://forum.inductiveautomation.com/u/CP5_Informatica)\ **Post date:** [September 25, 2026, 10:25am UTC](https://forum.inductiveautomation.com/t/the-pipeline-delay-blocks-are-not-cancelled/117187/1 "2026-09-25T10:25:53Z")
Good morning. I have designed an alarm notification pipeline that includes several **delay blocks**. When I attempt to **cancel** this Pipeline from the Gateway (_Services -\> Alarming -\> Pipelines -\> Pipeline Row -\> View Details_), it doesn't cancel. The same number of pipelines remains running. You can see this situation in the attached video: > **[Ignition Ticket #199733 - Pipeline blocks are not cancelled](https://wetransfer.com/downloads/ad7a1359e0f31d8d4f596e5c2936e80320260923112730/8da66c?t_exp=1790767650&t_lsid=7b8aa183-7890-4b95-a3db-9b75317752f6&t_network=link&t_s=download_link&t_ts=1790162850)** > > 1 file sent via WeTransfer, the simplest way to send your files around the world I understand that it's not canceled because there's a **delay block running** , but It is confusing that after clicking "Cancel," the cancellation is confirmed, yet the pipeline actually continues running because a delay block is currently executing. It should be possible to **forcibly cancel** the pipeline from the gateway, even if a delay block is running. Imagine a design flaw causes multiple alarms to trigger simultaneously, executing the same pipeline, which includes a delay block lasting several minutes. Currently, there is no way to force the cancellation of those pipelines. I believe the only solution is to restart the Ignition service at the operating system level. Best Regards.