Propagate a source correction through working tables — what should the operator record?
A publisher correction can affect a quoted field, a date or the identity of an item. Operational handling should preserve what was actually observed while correcting current permitted outputs. Identify the changed fields and their dependents before deciding that every table using the source needs the same blanket replacement.
Track the effect of a confirmed source correction without rewriting historical observations as if they never existed.
Record the currently inspectable correction link or returned field difference, avoiding speculation about the publisher's motivation or exact edit time. An explicit correction notice supports a stronger correction basis than two different observed values; preserve which kind of evidence actually justified the proposed patch.
If the correction cannot currently be inspected, label the patch pending rather than distributing an inferred replacement as confirmed source content. The final note should distinguish confirmed correction, unresolved difference and unsupported edit timing, preventing a reasonable patch from becoming an invented history of source changes.Capture the correction basis
Record the currently inspectable correction link or returned field difference, avoiding speculation about the publisher's motivation or exact edit time. An explicit correction notice supports a stronger correction basis than two different observed values; preserve which kind of evidence actually justified the proposed patch.
Scope affected fields
Create a patch proposal naming source_key, old_field_reference, corrected_value and affected_table_revisions; retain old content only where continued storage is permitted. A corrected publication date might move a row outside the working window, while corrected spelling might only affect display; scope the patch by field semantics.
Review dependent transformations
Check whether corrected dates alter window eligibility or corrected identifiers alter joins, not merely the visible descriptive cell. Inspect aggregates, exports and review queues that used the changed field, since a corrected visible table can coexist with an outdated derived count or membership set.
Apply an approved revision
Publish corrected derived tables under new revisions and mark prior working outputs superseded where appropriate instead of overwriting all lineage evidence. Do not leave an old identifying value in a public patch description if current policy prohibits retaining it; use a restricted reference or nonidentifying disposition.
Close with uncertainty
If the correction cannot currently be inspected, label the patch pending rather than distributing an inferred replacement as confirmed source content. The final note should distinguish confirmed correction, unresolved difference and unsupported edit timing, preventing a reasonable patch from becoming an invented history of source changes.
Keep the boundaries clear.
- Track the effect of a confirmed source correction without rewriting historical observations as if they never existed.
- Operational record: Capture the correction basis. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.