# Gateway Network Timout Issues **URL:** \ **Category:** Ignition\ **Tags:** ignition81, scripting\ **Created:** [September 11, 2024, 7:30pm UTC](https://forum.inductiveautomation.com/t/gateway-network-timout-issues/95869 "2024-09-11T19:30:10Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [September 11, 2024, 7:30pm UTC](https://forum.inductiveautomation.com/t/gateway-network-timout-issues/95869/1 "2024-09-11T19:30:10Z")
I'm helping a customer troubleshoot a strange issue that we've seen a few times, and I'm hoping that someone here has seen it or knows what is going on. There are three separate gateway systems, both redundant. Gateway A and B botch have an outgoing connection to Gateway C. During the normal course of activities on Gateway A and B, they do a system.util.sendRequest to Gateway C and expect a response back from Gateway C. Some time over the past day, something happened and the connection between Gateway A and Gateway C was disconnected and then re-connected. The gateway was showing all the connections as running, and the tag in the system folder was showing connected. However, and this is where the problem is, any sendRequest or sendMessage to Gateway C from Gateway A failed on timeout. I was able to get things going again by resetting the GAN from Gateway A to Gateway C in Gateway A's status page. After that all the things went back to communicating. Is there anything I can do to try and diagnose what is going on? This doesn't happen often, however when it does it takes someone to reset the connections where there doesn't appear to be anything wrong from a status point of view. Ideas? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [September 11, 2024, 7:33pm UTC](https://forum.inductiveautomation.com/t/gateway-network-timout-issues/95869/2 "2024-09-11T19:33:37Z")
Sounds like a bug to me. Open a ticket? ---
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [September 11, 2024, 7:42pm UTC](https://forum.inductiveautomation.com/t/gateway-network-timout-issues/95869/3 "2024-09-11T19:42:40Z")
The problem is that it is something that isn't really repeatable, and when it is broke their process is hamstrung until it is back up and running. I'm hoping to try and get some troubleshooting logs etc... that I can grab and send them into support when I open the ticket. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [September 11, 2024, 8:15pm UTC](https://forum.inductiveautomation.com/t/gateway-network-timout-issues/95869/4 "2024-09-11T20:15:39Z")
I'll bet there's some bug that kicks in when requests are unable to return their response to a calling gateway. Try setting up a message handler on "C" that just waits 30 seconds and returns some arbitrary object. Then fire a request from "A", wait 15 seconds, then break the network until the original request times out. Repeat a few times if necessary. (Well, probably not on your production gateways.) ---
**Author:** ![bschroeder](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bschroeder/32/13260_2.png) [@bschroeder](https://forum.inductiveautomation.com/u/bschroeder)\ **Post date:** [September 11, 2024, 8:35pm UTC](https://forum.inductiveautomation.com/t/gateway-network-timout-issues/95869/5 "2024-09-11T20:35:09Z")
Yeah I'll have to set something up in the lab and see if I can reproduce it. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [September 11, 2024, 9:31pm UTC](https://forum.inductiveautomation.com/t/gateway-network-timout-issues/95869/6 "2024-09-11T21:31:35Z")
I'm taking note that this is probably the only time @pturmel has ever recommended using something like `sleep` to delay execution of a script! 🤯 ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [September 11, 2024, 9:32pm UTC](https://forum.inductiveautomation.com/t/gateway-network-timout-issues/95869/7 "2024-09-11T21:32:16Z")
I'm fine with sleep() in dedicated threads and asynchronous threads. And when deliberately trying to break Ignition. 🤷‍♂️