I can’t seem to figure out why the GET /api/v2/screenrecordings endpoint returns a 404 Not Found error when querying recordings associated with our AP-Southeast-1 BYOC trunk sessions, despite the call data appearing correctly in the Interaction Search logs.
The system seems to drop the recording reference during the SIP registration phase, leaving the interaction ID orphaned in the analytics layer.