Trying to understand why our Architect flow throws a 502 Bad Gateway error when hitting the wfm:schedule:query endpoint during peak hours. We are running Genesys Cloud v24.5.0 in the Chicago environment. The flow is designed to route agents based on their current schedule adherence status, specifically checking if they are in a break or available state. The issue occurs consistently around 10:00 AM CT when the weekly schedule publish completes. The error log shows Connection reset by peer after a 30-second timeout. We have verified that the OAuth token used in the HTTP Request node has the necessary wfm:schedule:view permissions. The problem seems to spike when multiple agents trigger the flow simultaneously via shift swaps. Is there a known rate limit or a better way to cache the WFM data in Architect to avoid these timeouts? We need a reliable method to ensure agents are routed correctly without dropping calls due to API failures.