# Syslog filled with "(node:##) TimeoutOverflowWarning: ########## does not fit into a 32-bit signed integer"

**URL:** <https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966>\
**Category:** General\
**Created:** [8 June 2019 05:59 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966 "2019-06-08T05:59:13Z")\
**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:01 UTC](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966/8 "2019-07-06T08:01:21Z")

</div>

@Jesse305 did you get to the bottom of this, or have you just stuck with node 8.x for the moment. The same problem has been reported again.

> [@Node-RED 0.20.7 released](https://discourse.nodered.org/t/node-red-0-20-7-released/12955/2):
>
> Hi, Is there a known issue (yet) with timers/delays in 0.20.7? I upgraded earlier and my log file is a solid mountain of: (node:1192) TimeoutOverflowWarning: 3124648168 does not fit into a 32-bit signed integer. Timeout duration was set to 1. I'm not using setInterval(), timers, delays, or any timing things like that, this is a program that has been running for about a month with no issues.

---

_[View the full topic](https://discourse.nodered.org/t/syslog-filled-with-node-timeoutoverflowwarning-does-not-fit-into-a-32-bit-signed-integer/11966)._