Looking for advice on a persistent 500 Internal Server Error when querying the WFM Schedule Analytics endpoint. Our team in Chicago runs weekly adherence reports using GET /api/v2/wfm/schedule/analytics, but the call fails consistently between 2 PM and 4 PM CST. The payload includes standard filters for agent_group_id and date_range, yet the response returns a generic server error without useful details. We have verified that the agent IDs are active and the date range is valid. This issue started after the latest platform update last week. Is this a known issue with high-concurrency analytics queries? We need this data for our shift swap approvals and it is blocking our workflow. Any insights into debugging this or a workaround would be greatly appreciated. We are currently on version 2024-10 of the API. The error seems to correlate with the volume of active schedules being processed at that time. We have tried reducing the batch size but the issue persists. Looking for any community input on similar experiences or best practices for handling large schedule datasets in the analytics API. Thanks in advance for any help.