Encountering a 404 Not Found error when attempting to retrieve specific WebRTC softphone recordings via the /api/v2/recording/export endpoint during a legal discovery bulk export job. The issue appears isolated to digital channel interactions where the media_type is flagged as webrtc. While standard voice calls export successfully to our S3 bucket with correct metadata chain of custody, these WebRTC sessions return empty results or fail with recording_not_found. The Architect flow logs confirm the session was active and recorded for the required retention period. We are using the Recording API v2 with correct scopes (recording:read, recording:export). The environment is Genesys Cloud EU-West. Is there a known limitation with WebRTC media storage paths that causes this mismatch in the export manifest? We need to ensure full audit trail compliance for these digital interactions.