trying to understand why our bulk export jobs are failing with a 409 conflict error when we try to attach specific legal hold metadata tags via the Quality Management API. we are using the standard bulk export endpoint to pull recording artifacts from the last 30 days for a discovery request. the s3 integration is working fine for standard exports but when we add the legal hold parameters to the request body the job status moves to failed immediately. the error message says “resource conflict detected for metadata schema version”. we are on the latest api version and our timezone is set to Europe/London. the chain of custody requirements are strict so we cannot use the manual UI export method because it lacks the audit trail we need. has anyone seen this specific conflict error before? we checked the documentation and it mentions schema versioning but does not explain how to resolve the conflict programmatically. we need to ensure the metadata is preserved exactly as it was at the time of recording for legal compliance. any advice on how to bypass this or fix the schema mismatch would be appreciated. we are using python requests library version 2.28.1 to make the calls.