Network failure if App left running overnight. Can't ping router after sleep with Twingate running

Simple issue. Didn’t happen before. If I disconnect from Twingate, all connectivity immediately returns. If I disable Twingate before sleeping, there is no issue. There are periodic 5-minute checks of our relays, below are the logs from the period at which they first fail and never recover.

[2023-09-15T03:02:14.231225-07:00] [DEBUG] [client] Invoke NetworkConnectivityChanged {“Id”:“00842b50-f281-cf39-0f2a-da00e24c4c44”,“GroupId”:“20de2d6c-a4e0-496a-aa23-daaa7f2fc523”,“AdapterId”:“99671b5a-21ec-46c5-a064-4785947ddceb”,“IsConnected”:false,“IsConnectedToInternet”:false} [NetworkDiscoveryManager.HandleNetworkConnectivityChange]
[2023-09-15T03:02:14.231225-07:00] [INFO] [client] Internet connectivity changed on Interface=00842b50-f281-cf39-0f2a-da00e24c4c44 IsConnectedToInternet=False [NetworkMonitoringService.OnInternetConnectivityChanged]
[2023-09-15T03:02:14.231225-07:00] [DEBUG] [client] Handle the network change event. [ConnectionManager.NetworkChanged]
[2023-09-15T03:02:14.231225-07:00] [DEBUG] [libsdwan] Clear the bypass interface cache. [NetworkMonitoringService.NotifyOnNetworkChanged]
[2023-09-15T03:02:14.265013-07:00] [INFO] [client] Notify sdwan network change with dns = 127.0.0.1 [SdwanWrapper.NetworkChange]
[2023-09-15T03:02:14.265013-07:00] [INFO] [libsdwan] set_dns: 127.0.0.1 [NetworkMonitoringService.NotifyOnNetworkChanged]
[2023-09-15T03:02:14.265013-07:00] [DEBUG] [libsdwan] __configure_sdwan_dns: added “127.0.0.1” [.log]
[2023-09-15T03:02:14.265013-07:00] [DEBUG] [libsdwan] configure_viper_dns: ‘{“modules”:{“viper”:{“dns-proxy”:{“bypass-dnsserver-map”:[{“from”:“100.95.0.251”,“to”:“127.0.0.1”},{“from”:“100.95.0.252”,“to”:“127.0.0.1”},{“from”:“100.95.0.253”,“to”:“127.0.0.1”},{“from”:“100.95.0.254”,“to”:“127.0.0.1”}]}}}}’ [NetworkMonitoringService.NotifyOnNetworkChanged]
[2023-09-15T03:02:14.265013-07:00] [DEBUG] [libsdwan] sdwan_dns_set: DNS has been configured successfully [NetworkMonitoringService.NotifyOnNetworkChanged]
[2023-09-15T03:02:14.265013-07:00] [DEBUG] [libsdwan] Bypass interface cache updated: index=19, local_addr=3232235956, gw_addr=3232256585 [.log]
[2023-09-15T03:02:14.269092-07:00] [DEBUG] [libsdwan] reconfigure_direct_connect_socket: set the size of UDP socket buffers to 4194304 bytes [.log]
[2023-09-15T03:02:14.269092-07:00] [DEBUG] [libsdwan] reconfigure_direct_connect_socket: reconfigured direct connect socket [.log]
[2023-09-15T03:02:14.269092-07:00] [DEBUG] [libsdwan] on_network_change: reconnecting hydra transports to access nodes [.log]
[2023-09-15T03:02:14.269092-07:00] [DEBUG] [libsdwan] [stun] sdwan::stun::stun_service_t::on_bus_event: resetting direct connect info due to network switch [.log]
[2023-09-15T03:02:14.269092-07:00] [DEBUG] [libsdwan] [stun] sdwan::stun::stun_service_t::update_public_address: sent STUN request to 34.102.46.42:3478 [.log]
[2023-09-15T03:02:15.261197-07:00] [DEBUG] [libsdwan] [stun] sdwan::stun::stun_service_t::update_public_address: sent STUN request to 34.102.46.42:3478 [.log]
[2023-09-15T03:02:17.261727-07:00] [DEBUG] [libsdwan] [stun] sdwan::stun::stun_service_t::update_public_address: sent STUN request to 34.102.46.42:3478 [.log]
[2023-09-15T03:02:21.254733-07:00] [DEBUG] [libsdwan] [stun] sdwan::stun::stun_service_t::update_public_address: sent STUN request to 34.102.46.42:3478 [.log]
[2023-09-15T03:02:29.258407-07:00] [DEBUG] [libsdwan] [stun] sdwan::stun::stun_service_t::update_public_address: sent STUN request to 34.102.46.42:3478 [.log]
[2023-09-15T03:02:45.257254-07:00] [DEBUG] [libsdwan] [stun] sdwan::stun::stun_service_t::update_public_address: sent STUN request to 34.102.46.42:3478 [.log]
[2023-09-15T03:03:06.151717-07:00] [DEBUG] [libsdwan] [stun] sdwan::stun::stun_service_t::get_stun_addresses: asking load balancer https:// relays.twingate .com for the addresses of STUN server instances [.log]
[2023-09-15T03:03:06.151717-07:00] [DEBUG] [libsdwan] relaybalancer::get_instance: “https:// relays.twingate .com” [.log]
[2023-09-15T03:03:06.151717-07:00] [DEBUG] [libsdwan] http::request::send_request: GET “https:// relays.twingate .com/api/v2/metadata” text/plain [.log]
[2023-09-15T03:03:11.149389-07:00] [WARN] [libsdwan] http::request::handle_response: GET “https:// relays.twingate. com/api/v2/metadata” failed - dns error: 11003 (non-recoverable failure in name resolution), socket error: 0 (The operation completed successfully.), tls error: 0 ((null)) [.log]
[2023-09-15T03:03:12.151097-07:00] [DEBUG] [libsdwan] [stun] sdwan::stun::stun_service_t::get_stun_addresses: asking load balancer https:// relays.twingate .com for the addresses of STUN server instances [.log]

Hi @Zac_CalypsoAI! Following up here - if you run the latest versions of the client and connectors, are you still running into the same issues as before?