Is it possible to force a retry on a bulk export job that fails with a 409 Conflict when updating legal hold metadata? We are processing discovery requests for digital channels (chat and SMS) in the eu-west-2 region. The export jobs initiate correctly, but the post-processing step that applies the legal hold tag fails intermittently.
The error response indicates a version mismatch on the recording_export_job resource. This happens even when we use the If-Match header with the latest ETag retrieved from the initial job creation. The API documentation here suggests that the export job state should be immutable after creation, yet the legal hold attachment process seems to require a state update.
We have verified that no other processes are modifying the job. The issue persists across different export scopes. Is this a known limitation with the current version of the Analytics Export API? Or is there a specific sequence for applying legal holds to avoid the 409 error during the chain of custody verification?