Struggling to figure out why the bulk export job fails when attempting to include specific legal hold metadata fields. The standard export works fine, but adding the legal_hold_status attribute triggers an immediate failure.
- Initiate a bulk export job via
POST /api/v2/recordings/exports. - Include the filter
legalHoldStatus=trueand request thelegalHoldIdin thecolumnsarray. - The job status moves to
QUEUEDthen immediately toFAILED.
The error log shows:
{"code": "forbidden_resource", "message": "Access denied to restricted metadata fields for user role: recording_export_specialist"}
This is confusing because the service account has recording:bulk:export permissions. We are using the Python SDK v4.5.1. The issue occurs consistently in the London region. Other metadata like callDirection exports without issue. Is there a separate permission scope required for legal discovery metadata fields? The documentation does not mention any additional scopes beyond the standard export permissions. This is blocking our current discovery request timeline.