FindingcurrentGTM data

Long-open cases fall outside recency windows

Keep a record if it's recent or still open.

SymptomAn agent can't find a support case the customer is still waiting on, because the case was opened before your ingest cutoff.

A recency window is the standard cost control for ingest: load the last N months and skip the rest. For most objects, old means finished.

Open support cases don't follow that, because the backlog can skew old and leave many open cases older than a 12-month cutoff. The risk is greatest for a window on created date, or on cases nobody has touched inside it.

Those are the cases people ask about, yet a 12-month window can drop much of the open support work while keeping the recently closed cases, so the rule is recent or still open.

Check your setup read-only

Count open support cases by the date each case was opened. Find the share older than the cutoff in your ingest or retrieval config. Any open case outside the window is live work the window drops.

Passes ifNo open support case is older than your ingest or retrieval cutoff. Otherwise, your jobs keep open cases regardless of age.

Access needed:crm-readlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Keep a record if it was modified inside the window or is still open, whatever its age.
  2. 02Define open per object from its status field, such as not closed and not resolved.
  3. 03Apply the same rule to any object with long-lived open states, such as support cases and opportunities.
  4. 04Count open records older than a cutoff before choosing the cutoff. If that share is material, widen the rule, not the window.
Applies ifYour ingest or retrieval config reads only recent CRM records, cases or activity, and customer-health views or alerts rest on them.

← 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.