Quick question about the stability of the /v2/recordings/screen endpoint during trunk failover events. We see immediate 500 Internal Server Error responses when traffic shifts to secondary BYOC providers in Asia/Singapore, despite standard call recordings succeeding. Is there a known dependency on primary trunk metadata for screen session initialization?