FindingcurrentGTM data

A soft delete may not move your copy's modified time

Freshness gates keyed on your copy's modified time skip soft deletes.

SymptomRecords deleted in the CRM keep appearing in answers, while in your warehouse copy only the connector's sync column shows they were touched.

Incremental pipelines pick what to reprocess by the CRM's last-modified time. It's the standard freshness gate, and the right clock for ordinary edits.

A soft delete is the exception. In the CRM, a delete may restamp the record itself. But a connector learns about deletes through a separate deleted-records call, so the copy of the modified time in your warehouse never moves; only the connector's sync column does. Fivetran's Salesforce documentation says it captures soft-deleted records through the sObject Get Deleted endpoint.

A gate keyed on that copied stamp then sees nothing new. The delete is skipped, and the record keeps feeding answers as if it were live.

A job that reads the CRM directly with a standard query never sees deleted rows at all; only a query that includes deleted rows returns them.

The answer is two clocks with two jobs.

  • The sync stamp decides what gets processed.
  • The CRM stamp stays the displayed time, because it says when the business record changed.

In a synthetic test set with 50 soft-deleted records in a warehouse copy, a reprocess gate on the copied CRM modified time left all 50 still served; a gate on the sync stamp left none. The set shows the mechanism, not how common it is.

Check your setup read-only

List records in the CRM's recycle bin from the last 30 days. Compare each record's modified time in your warehouse copy with the connector's sync time. Check whether only the sync time moved. Check whether your pipeline gates on the copied modified time. If both are true, those records never reached you as gone.

Passes ifEvery record in the last 30 days of the recycle bin reached your pipeline as gone. Otherwise, your freshness gate keys on the sync time.

Access needed:crm-readlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Gate reprocessing on the connector's sync stamp, not the CRM's last-modified time.
  2. 02Keep the CRM's last-modified time as the "changed at" time you show people and agents.
  3. 03Read the deleted flag on every record the sync stamp surfaces. Retire the record downstream when the flag is true.
  4. 04Use the query mode that includes deleted records when reading the CRM directly for deletes.
  5. 05Apply the same two-clock gate at every layer that keeps its own copy, not only the first load.
Applies ifA job config in your setup reads the CRM incrementally by last-modified time, such as an incremental cleanup or an enrichment pass.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.