The recording export job terminates with HTTP 422 Unprocessable Entity. The payload contains standard chain of custody fields but excludes the routing_script_id from the digital channel metadata. Our S3 integration relies on this ID for legal hold tagging. The API documentation states this field is optional, yet the validation layer rejects the request when it is missing. Is there a strict requirement for this attribute in the current bulk export endpoint?
Ah, yeah, this is a known issue…
Cause: The bulk export validation enforces strict schema alignment for legal hold integrations, overriding the general API documentation that marks routing_script_id as optional.
Solution: Include a null value for the field to satisfy the validator: "routing_script_id": null.