No idea why this is happening, the Screen Recording API is failing with a 500 Internal Server Error when attempting to fetch recording metadata for calls routed through our AP-Southeast-1 BYOC trunks. The issue seems isolated to sessions where the SIP registration state fluctuated during the call, triggering a carrier failover.
We are using the /api/v2/recordings/screens/{recordingId} endpoint to pull data for our WEM integration, which correlates screen activity with trunk performance metrics. The system works fine for standard PSTN routes, but fails consistently for these specific BYOC sessions. The error payload suggests a backend database lock or timeout, but the recording file itself exists in S3.
{
"errors": [
{
"code": "INTERNAL_SERVER_ERROR",
"message": "Unable to retrieve recording metadata. Database connection pool exhausted."
}
]
}
Has anyone encountered this specific database lock issue when querying screen recordings for calls that experienced mid-call trunk failover? We need to ensure our analytics pipeline captures this data without triggering these backend timeouts.