# Long-open cases fall outside recency windows

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

By Ki Moon · 2026-08-27 · finding · current
Canonical: https://kihmoon.com/bench-notes/p/open-cases-outlive-recency-windows/

**Symptom:** An 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 if:** No open support case is older than your ingest or retrieval cutoff. Otherwise, your jobs keep open cases regardless of age.

**Access needed:** crm-read, local-config

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

1. Keep a record if it was modified inside the window or is still open, whatever its age.
2. Define open per object from its status field, such as not closed and not resolved.
3. Apply the same rule to any object with long-lived open states, such as support cases and opportunities.
4. Count open records older than a cutoff before choosing the cutoff. If that share is material, widen the rule, not the window.

**Applies if:** Your ingest or retrieval config reads only recent CRM records, cases or activity, and customer-health views or alerts rest on them.

**Skip if:** Your ingest config loads full history for every object.

Tags: cost, freshness, crm
