Data Action returning 500 when mapping legal hold metadata for S3 export

Does anyone understand why the ‘Put Record in S3’ data action fails with a 500 Internal Server Error when attempting to inject custom legal_hold tags into the filename? The flow works for standard exports but breaks specifically when the metadata payload exceeds 256 characters.

  • Verified the S3 bucket policy allows PUT requests and the IAM role has full access.
  • Tested with a simplified payload containing only the recording ID, which succeeded without error.