I have a winform app that will run either minimized or in the system tray. Part of its job is to display incoming caller info. I am using the C# SDK to successfully authenticate, create the subscription and then receive notification information. The problems start when I just leave the program running and no new events are coming in simulating the use case where someone leaves the program running overnight (or an extended lunch). We start to see first chance web socket exceptions, null exceptions and eventually a code break will happen and a final error will indicate that objects have been optimized away. These errors are coming from the SDK code and don't bubble up through any try/catch code so that I could handle the error. The application is dead simple at this point. It connects, authorizes, creates a subscription and listens via callbacks. Is there a method I need to call on a timer to keep the objects alive?