# Delay and trigger reset after a deploy

**URL:** <https://discourse.nodered.org/t/delay-and-trigger-reset-after-a-deploy/42029>\
**Category:** General\
**Created:** [4 March 2021 16:18 UTC](https://discourse.nodered.org/t/delay-and-trigger-reset-after-a-deploy/42029 "2021-03-04T16:18:14Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![fmarzocca](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fmarzocca/32/35901_2.png) [@fmarzocca](https://discourse.nodered.org/u/fmarzocca)\
**Post date:** [4 March 2021 16:18 UTC](https://discourse.nodered.org/t/delay-and-trigger-reset-after-a-deploy/42029/1 "2021-03-04T16:18:14Z")

</div>

I noticed that every trigger or delay in use (I mean: running their time count) are reset and stopped during a deploy.  
Now, I have many flows deployed and running, while continuing programming other flows, so this behaviour can bring to very bad situations in my environment.

Is there any way to avoid this? Stopping coding is not an option...

Thanks  
Fabio

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [4 March 2021 16:27 UTC](https://discourse.nodered.org/t/delay-and-trigger-reset-after-a-deploy/42029/2 "2021-03-04T16:27:13Z")

</div>

> [@fmarzocca](#):
>
> Is there any way to avoid this?

Use node deploy instead of full deploy should help

---

<div class="post-metadata">

**Author:** ![fmarzocca](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fmarzocca/32/35901_2.png) [@fmarzocca](https://discourse.nodered.org/u/fmarzocca)\
**Post date:** [4 March 2021 16:31 UTC](https://discourse.nodered.org/t/delay-and-trigger-reset-after-a-deploy/42029/3 "2021-03-04T16:31:40Z")

</div>

Hi Steve,

I tried that but the Deploy button keeps red, and the modified node(s) has still the blue circle on top (indicating that it needs to be deployed).

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [4 March 2021 16:32 UTC](https://discourse.nodered.org/t/delay-and-trigger-reset-after-a-deploy/42029/4 "2021-03-04T16:32:42Z")

</div>

You need to press the button after changing deploy mode.

---

<div class="post-metadata">

**Author:** ![fmarzocca](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/fmarzocca/32/35901_2.png) [@fmarzocca](https://discourse.nodered.org/u/fmarzocca)\
**Post date:** [4 March 2021 16:33 UTC](https://discourse.nodered.org/t/delay-and-trigger-reset-after-a-deploy/42029/5 "2021-03-04T16:33:16Z")

</div>

Aaah!  
My bad, sorry.

And thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [18 March 2021 16:33 UTC](https://discourse.nodered.org/t/delay-and-trigger-reset-after-a-deploy/42029/6 "2021-03-18T16:33:40Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.