Could someone explain why our Analytics reporting endpoints are returning HTTP 503 Service Unavailable errors specifically during the weekly WFM schedule publish window? We are operating in America/Chicago timezone and the publish job runs automatically every Sunday at 2:00 AM CT. The issue started after we upgraded to Genesys Cloud version 2024-2.0. When the POST /api/v2/wfm/schedules/publish endpoint is triggered, our custom Python script that polls GET /api/v2/analytics/conversations/queues for adherence metrics begins failing with 503. The error response includes Retry-After: 120 header, but the failures persist for approximately 15 minutes after the publish job completes successfully. We have verified that the WFM dashboard shows the schedule as published, yet the analytics backend seems to be in a degraded state. We are using the genesys-cloud-python-sdk version 10.4.2 and have implemented exponential backoff, but the volume of failed requests is impacting our real-time adherence alerts. The specific error message in the logs is Service temporarily unavailable due to high load or maintenance. This is critical because our shift swap approvals rely on accurate historical adherence data, which becomes stale during this window. We have checked the System Status page and it shows all green, but the API latency spikes significantly. Is there a known limitation with concurrent WFM publishing and Analytics queries in this release? We need to ensure our workforce management workflows remain uninterrupted. Any insights into whether this is a caching issue or a resource contention problem would be greatly appreciated. We are looking to optimize our query timing or implement a more robust fallback mechanism. Thank you for the help.