Is it possible to enforce legal hold tags in Architect digital flows?

Architect & Flows
1

Configuring an Architect flow for WhatsApp transcripts. The flow sets the legal_hold attribute to true, but the subsequent S3 export via the Recording API omits this metadata. The API returns 200 OK, yet the chain of custody is broken for discovery requests.

Is it possible to force the metadata attachment within the flow logic itself, or does this require a specific IAM permission on the S3 bucket policy?

2

The problem here is…

Is it possible to force the metadata attachment within the flow logic itself?

Architect flows don’t push metadata to S3 exports. You need to tag the interaction via the Platform API before export. Check your JMeter logs for 429s on /api/v2/interactions during high concurrency. The API enforces strict rate limits, so batching requests might be necessary to avoid throttling.