PROBLEM · STALE ENTITLEMENTS
The data is right. It is just late.
Stale entitlements look like leaks but are actually timing problems. Telling the difference requires snapshot timestamps and a defined freshness threshold.
What this problem looks like
The entitlement snapshot is older than the billing snapshot. The comparison may show a disagreement that has already been resolved in the source system but has not yet propagated.
- Scheduled sync has not run since the last subscription change
- Connector deployment is delayed or failing
- Snapshot marked complete with stale data
- Clock skew between systems
Detection method
SubSync Guard requires both snapshots to be complete and within a freshness threshold before reconciling. If either snapshot is stale, the run is rejected with a clear error rather than producing a misleading finding.
- Complete-snapshot flag on both sides
- Row count and capture time recorded
- Seven-day freshness threshold by default
- Explicit rejection of stale inputs
Operational response
Trigger a manual sync from the monitoring page. Confirm both snapshots are marked complete and recent. Re-run reconciliation. If the finding disappears, it was lag. If it persists, it is a real disagreement.
Frequently asked
What happens if I reconcile with stale data?
The run is rejected. The system refuses to produce findings from incomplete or stale snapshots.
Can I change the freshness threshold?
The threshold is part of the reconciliation policy. Changing it requires a code or configuration change.