The POST /api/v2/analytics/interactions/details endpoint won’t parse the routing filter correctly when it tries to cross-reference predictiveRoutingScore against the custom topicModelId wired into Architect. SDK v2.14.3 on the SGT-based worker throws a validationError on the timeGroup array every single time the flow hits the Wait for Routing block. Payload matches the OpenSpec exactly but the gateway still rejects the routingStrategy enum, leaving the retry loop burning CPU doing jack all.
Cause: The parser bricks when predictiveRoutingScore hits topicModelId in the timeGroup array. That eastern window sync thread hit the same brick. System treats the custom model like a bad timestamp.
Solution: Drop the topicModelId filter. Switch to queueId instead. Pacing metrics stay clean and abandonment rates won’t get skewed by the timeout loop.