# Node-red-contrib-timeouttrigger

**URL:** <https://discourse.nodered.org/t/node-red-contrib-timeouttrigger/85419>\
**Category:** Developing Nodes\
**Created:** [11 February 2024 15:23 UTC](https://discourse.nodered.org/t/node-red-contrib-timeouttrigger/85419 "2024-02-11T15:23:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sineos](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sineos/32/3440_2.png) [@Sineos](https://discourse.nodered.org/u/Sineos)\
**Post date:** [11 February 2024 15:23 UTC](https://discourse.nodered.org/t/node-red-contrib-timeouttrigger/85419/1 "2024-02-11T15:23:56Z")

</div>

Dear all,

I have published the node [node-red-contrib-timeouttrigger](https://github.com/Sineos/node-red-contrib-timeouttrigger).

There seems to be an issue that I cannot make heads or tails of: [No message pass through after reinstallation of the node · Issue #5 · Sineos/node-red-contrib-timeouttrigger · GitHub](https://github.com/Sineos/node-red-contrib-timeouttrigger/issues/5)

It seems that the node stops processing incoming messages after exporting / importing existing flows. It will pick up processing again after simply opening it, closing it and redeploying.

The node itself is not a complex thing and I'm also not able to reproduce this unwanted behavior. Also, my Google Kung Fu seems weak and did not turn up anything useful.

Has anybody experienced similar? Any hint where to even start searching would be highly appreciated. Many thanks in advance.

---

<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:** [11 February 2024 15:47 UTC](https://discourse.nodered.org/t/node-red-contrib-timeouttrigger/85419/2 "2024-02-11T15:47:35Z")

</div>

That sounds to me like an issue with field validation. The latest version of node-red is more strict with validations. To replicate I suggest starting with fresh install of node red 2.x. Install your node and configure it. Then upgrade node-red to the latest and restart. I suspect they will show the red triangle.

Edit, you might need to start with an older version of your node too and upgrade that also.

---

<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:** [11 February 2024 15:56 UTC](https://discourse.nodered.org/t/node-red-contrib-timeouttrigger/85419/3 "2024-02-11T15:56:56Z")

</div>

You likely need to also default the `passthrough` variable in the server side

```auto
this.passthrough = n.passthrough ?? true; // default to true if value is nullish

```

If the node is already on the workspace but does not have a `passthrough` value in the export json, it will be missing from the server side.

This can happen when node packages are upgraded with new capabilities but an old flow does not have these new properties.

---

<div class="post-metadata">

**Author:** ![Sineos](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sineos/32/3440_2.png) [@Sineos](https://discourse.nodered.org/u/Sineos)\
**Post date:** [11 February 2024 17:36 UTC](https://discourse.nodered.org/t/node-red-contrib-timeouttrigger/85419/4 "2024-02-11T17:36:23Z")

</div>

Thank you very much for your input.

> [@Colin](#):
>
> To replicate I suggest starting with fresh install of node red 2.x. Install your node and configure it. Then upgrade node-red to the latest and restart. I suspect they will show the red triangle.

In fact, I already tried this from NR v2.2. Did not give me any issue. Thanks a lot, nevertheless.

> [@Steve-Mcl](#):
>
> You likely need to also default the `passthrough` variable in the server side

That did the trick. In fact, starting with timeouttrigger v0.0.2 (without passthrough) and importing to an already installed v0.0.4 made it fail just like described.  
Implementing the server-sided initialization fixed it.  
Many thanks! This would have been a long and tedious search without your input!

---

<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:** [25 February 2024 17:37 UTC](https://discourse.nodered.org/t/node-red-contrib-timeouttrigger/85419/5 "2024-02-25T17:37:20Z")

</div>

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