Is it possible to configure the BYOC Edge instance to prioritize WFM schedule publish traffic over standard media streams during our weekly publishing window in the America/Chicago timezone? We are currently running Genesys Cloud CX with a BYOC Edge deployment in the US East region, and our workforce management team has noticed a significant degradation in API response times specifically when the POST /api/v2/wfm/schedules/publish endpoint is executed. The issue manifests as intermittent 504 Gateway Timeout errors when agents attempt to view their updated schedules or request shift swaps within the first 15 minutes of the publish job completing. Our current Edge configuration is set to default load balancing, but we suspect that the high volume of concurrent API calls generated by the schedule publish process is saturating the available throughput on the Edge node, causing downstream timeouts for the WFM microservices. We have verified that the network connectivity between the Edge node and the Genesys Cloud core is stable, and there are no packet loss issues reported by the network team. However, the latency spikes are consistently correlated with the start of our weekly publish job, which typically occurs on Tuesday mornings at 06:00 CT. We are using the latest version of the Genesys Cloud SDK for our internal integrations, and the error logs indicate that the Edge node is dropping connections due to resource exhaustion. We have tried adjusting the timeout settings in our internal scripts, but this only delays the error rather than resolving the underlying connectivity issue. The workforce management team is under pressure to ensure that agent schedules are visible immediately after the publish job completes, and these delays are causing confusion and unnecessary support tickets. We need a way to ensure that the WFM API calls are not impacted by the media stream traffic on the Edge node, or perhaps a configuration change that allows for better resource allocation during peak publish times. Any insights into how other organizations with similar BYOC Edge setups handle this concurrency issue would be greatly appreciated. Are there specific Edge configuration parameters that can be tuned to improve the stability of WFM API calls during high-load periods?