# Node-RED 0.20.7 released

**URL:** https://discourse.nodered.org/t/node-red-0-20-7-released/12955
**Category:** News
**Created:** [5 July 2019 14:43 UTC](https://discourse.nodered.org/t/node-red-0-20-7-released/12955 "2019-07-05T14:43:38Z")
**Posts on this page:** 1
**Showing post:** 8

<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: [6 July 2019 08:03 UTC](https://discourse.nodered.org/t/node-red-0-20-7-released/12955/8 "2019-07-06T08:03:46Z")

</div>

Also did you just upgrade node red or did you upgrade nodejs too? The problem has been reported previously with node 10.x and apparently it went away with a reversion to node 8.x.

> [@Syslog filled with "(node:##) TimeoutOverflowWarning: ########## does not fit into a 32-bit signed integer"](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966):
>
> Hello, My syslog is being filled with variations of the following error messages (this is just a short excerpt): (node:1215) TimeoutOverflowWarning: 2587711790 does not fit into a 32-bit signed integer. Timeout duration was set to 1. (node:1215) TimeoutOverflowWarning: 2587711789 does not fit into a 32-bit signed integer. Timeout duration was set to 1. (node:1215) TimeoutOverflowWarning: 2587711788 does not fit into a 32-bit signed integer. Timeout duration was set to 1. (node:1215) Tim…

---

_[View the full topic](https://discourse.nodered.org/t/node-red-0-20-7-released/12955)._