My configuration keeps failing… We are deploying a Genesys Cloud Edge Bring Your Own Container (BYOC) solution for a multi-tenant AppFoundry integration. The container is packaged as a custom connector to handle asynchronous data processing outside the main cluster. While the container starts and passes the initial health checks in the Edge environment (v1.0), outbound POST requests from the connector to our external service endpoint consistently fail with a 502 Bad Gateway error after approximately 24 hours of uptime. The logs indicate the connection is reset by the peer, suggesting the Edge network proxy might be terminating the idle TCP connections prematurely, despite the keep-alive headers being set. We are using the standard Edge SDK for container initialization. The issue does not replicate in our local dev environment using the Edge simulator. Has anyone encountered this specific timeout behavior with long-lived connections in Edge BYOC? We need to determine if this is a configuration issue within the container manifest or a limitation of the Edge networking layer.