Looking for advice on resolving a persistent 500 Internal Server Error when querying real-time conversation details for calls routed through our AP-SE-2 BYOC trunks. The endpoint /api/v2/analytics/conversations/details/realtime fails specifically when the carrierId attribute is included in the filter, despite the Architect flow setting the attribute correctly.
HTTP 500 Internal Server Error
Message: Failed to process analytics request for trunk context AP-SE-2-BYOC-01
This behavior started after the latest Genesys Cloud release. Is this a known limitation with BYOC trunk metadata in the analytics engine?