What it requires. The org's own retention promise and what the platform actually keeps disagree - transcripts, prompts, grounded record values and audit rows.
Why it matters. A stated retention of "none" on a connection record says nothing about what the orchestration around it keeps. Where that platform logs every step's input and output, a single execution can hold the same customer's pricing metadata three times over, alongside their client name and instance URL: a promise made in one system and not kept by another. Note the audit surface is not in Salesforce core, so the check reaches beyond the org's own configuration.
How to fix it. Reconcile the published retention policy against what each platform in the path actually stores, and change whichever is wrong - usually the system, sometimes the promise.
Source. Retention root-cause record, August 2026; Einstein Trust Layer audit documentation
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.