Why does this setting trigger a server-side failure when attempting to aggregate quality evaluation data across our distributed BYOC infrastructure? We are running the WFM Quality API against fifteen distinct BYOC trunks located in AP-Southeast-1. The endpoint /api/v2/wfm/quality/evaluations returns a consistent HTTP 500 Internal Server Error when the query parameters include trunk-specific metadata filters. This behavior is isolated to conversations routed through our carrier failover logic, specifically when the SIP registration state transitions during peak load. The payload structure adheres strictly to the v2.1 schema documentation, yet the response body contains no actionable error details beyond the generic server error message. We have verified that the trunk credentials are valid and the outbound routing rules are correctly applied in the Architect flow. The issue persists regardless of the SDK version used, suggesting a backend processing limitation rather than a client-side configuration error. We require clarification on whether there is a known limitation with aggregating quality scores for BYOC trunks that utilize dynamic carrier failover, or if this represents a defect in the current API implementation.