# Problem with the trigger node, after deploy

**URL:** <https://discourse.nodered.org/t/problem-with-the-trigger-node-after-deploy/14404>\
**Category:** General\
**Created:** [16 August 2019 18:14 UTC](https://discourse.nodered.org/t/problem-with-the-trigger-node-after-deploy/14404 "2019-08-16T18:14:06Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexsahka](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/alexsahka/32/7897_2.png) [@alexsahka](https://discourse.nodered.org/u/alexsahka)\
**Post date:** [16 August 2019 18:14 UTC](https://discourse.nodered.org/t/problem-with-the-trigger-node-after-deploy/14404/1 "2019-08-16T18:14:06Z")

</div>

I'm using the trigger node a lot, in different nodes (trigger, then wait for new messages - extend time, if new message) this way, with different timing from 1 sec to 10 minutes. And I noticed it is not working properly if I hit the deploy button, while I'm working for example on different flow, all trigger nodes stops on any flow without any message, silently.

How can I improve this, or use different node to replace the trigger node?

Thanks.

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/2X/4/4123edfc4f79279603087abf44067fb55c0455f1.png)

---

<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:** [16 August 2019 18:25 UTC](https://discourse.nodered.org/t/problem-with-the-trigger-node-after-deploy/14404/2 "2019-08-16T18:25:40Z")

</div>

Are you doing full deploy? That will reinitialise all nodes. Use the 3rd option on the deploy drop down (only modified nodes)

---

<div class="post-metadata">

**Author:** ![alexsahka](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/alexsahka/32/7897_2.png) [@alexsahka](https://discourse.nodered.org/u/alexsahka)\
**Post date:** [16 August 2019 18:37 UTC](https://discourse.nodered.org/t/problem-with-the-trigger-node-after-deploy/14404/3 "2019-08-16T18:37:17Z")

</div>

If I deploy only modified nodes node-red is not deploying properly (or it is designed this way).  
Also the deploy button still red and I think that everything is not deployed.

Simple check: after partial deploy try to refresh browser and see whats happened.  
Or my node red is not working properly?

---

<div class="post-metadata">

**Author:** ![bakman2](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bakman2/32/6207_2.png) [@bakman2](https://discourse.nodered.org/u/bakman2)\
**Post date:** [16 August 2019 19:01 UTC](https://discourse.nodered.org/t/problem-with-the-trigger-node-after-deploy/14404/4 "2019-08-16T19:01:55Z")

</div>

A modified node deploy may not always work properly in combination with certain nodes as they may be depending on eachother. I always use modified flows (not full) and use seperate flows to test/setup the trigger node before they end up in a collection of flows. That way my triggers don't get cleared.

---

<div class="post-metadata">

**Author:** ![alexsahka](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/alexsahka/32/7897_2.png) [@alexsahka](https://discourse.nodered.org/u/alexsahka)\
**Post date:** [16 August 2019 19:19 UTC](https://discourse.nodered.org/t/problem-with-the-trigger-node-after-deploy/14404/5 "2019-08-16T19:19:03Z")

</div>

I think I need setup separate Node Red (Docker) for testing purposes and keep one for Production with minimum Deployment.

---

<div class="post-metadata">

**Author:** ![neoyang](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/neoyang/32/35846_2.png) [@neoyang](https://discourse.nodered.org/u/neoyang)\
**Post date:** [24 January 2021 16:25 UTC](https://discourse.nodered.org/t/problem-with-the-trigger-node-after-deploy/14404/6 "2021-01-24T16:25:32Z")

</div>

I have the same issue with you.  
and I also thought so, it's a better solution to have a testing HA server.  
But finally, I found it's not easy to do that.  
when the project getting more complicate the testing HA more helpless.  
Wish someone here can help us on this issue.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [24 January 2021 17:39 UTC](https://discourse.nodered.org/t/problem-with-the-trigger-node-after-deploy/14404/7 "2021-01-24T17:39:21Z")

</div>

Welcome to the forum

This thread is a year old so I suggest that you start a new thread for your problem and describe exactly what you are seeing. Also tell us about your environment. If you are not using the latest version of node-red then upgrade to that first.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [24 January 2021 17:39 UTC](https://discourse.nodered.org/t/problem-with-the-trigger-node-after-deploy/14404/8 "2021-01-24T17:39:52Z")

</div>


