# A record's age is not the age of your sync

Report the CRM's last-edited date and the sync time as two separate facts.

By Ki Moon · 2026-10-29 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/record-age-is-not-sync-lag/

**Symptom:** An agent tells a user their data is stale when one record simply hasn't been edited in months.

A CRM's last-modified date says when someone last edited a record, and says nothing about when your copy was last refreshed. When an agent sees an old date and calls the data stale, it merges the two.

Two clocks are at work here, and they track different things.

- Last modified: when a person or process last edited the record in the CRM.
- Sync time: when your system last read it.
- A record can be old in the CRM and current in your copy.

Mixing the two sends users after the wrong problem. Told their data is stale, they doubt the sync and every answer built on it, even though all that happened is that one record hasn't been touched.

Saying both dates avoids that confusion, since last edited in the CRM is a fact about the account and last synced is a fact about the pipe.

Salesforce keeps two last-edited dates, so say which one you report. LastModifiedDate moves when a user or an integration edits the record, while SystemModstamp also moves for system changes.

## Check your setup (read-only)

Read the 10 most recent answers where your agent comments on freshness. Compare each answer with the record's CRM last-modified date and the last run time in your sync job's log. Any answer that blames the sync for an old last-modified date conflates the two.

**Passes if:** All 10 sampled freshness answers report the record's last-modified date and the last sync time as separate facts.

**Access needed:** agent-transcripts, crm-read, scheduler

## If it fails (changes to make later, not part of the check)

1. Give the agent the CRM's last-modified date and your last sync time as 2 separately named fields. Add both fields to every record the agent reads.
2. Have the agent describe freshness with both dates: the last edit in the CRM and the last sync.
3. Call the sync stale only when the sync time is old. Report an old last-edited date as its own fact about the record, not as a sync problem.
4. Say that a record hasn't been edited when the record is old but freshly synced. Name the date.

**Applies if:** Your agent or digest output tells sellers how current a CRM record is, such as a contact's title or an account's last activity.

**Skip if:** Your agent transcripts show no comment on freshness, only field values.

Tags: freshness, agents, crm
