SIP 408 Timeout aggregation gap in BYOC Analytics API

Stuck on a data gap in the Genesys Cloud Analytics API (v2.0) regarding SIP 408 Timeout errors on our 15 APAC BYOC trunks.

The GET /api/v2/analytics/details endpoint returns empty result sets for these specific 408 codes despite them appearing in real-time Architect logs, causing a skew in our carrier failover reporting. Is there a known latency or filtering issue with how 408 timeouts are aggregated in the reporting database versus the live event stream?