The stream engine keeps killing my WebSocket link the second I push a time window matrix into the subscription payload. Tried capping maximum concurrent connection limits at three, swapped the metric type references and granularity directives to match the docs, and wrapped the atomic handshake operations in an explicit automatic reconnection trigger, but the format verification callback just throws a validation error every time when I send this payload through the subscribe() method for the metric subscriber: {“metrics”: [{“type”: “real-time-interaction”, “granularity”: “minute”, “window”: {“start”: “now”, “duration”: 300}}], “validation”: {“metric_availability”: true, “data_aggregation_verification”: “strict”}, “callbacks”: {“onData”: “sync_external_dashboard”, “onLatency”: “track_freshness”, “onAudit”: “log_governance”}}. Connection drops right after the handshake completes, and it’s impossible to figure out if the stream engine constraints are rejecting the window matrix or if the Python SDK is mishandling the reconnection trigger while I’m still getting that handshake drop on the third retry cycle.