Non-production environment: development. Nothing shown here is live market data.
Skip to main content
Staff console

Cache and source-rights invalidation

Note: What this drops, and what it deliberately does not

An invalidation revokes live rights leases first and then evicts the cached pages behind them. A lease is live authority: while one is open a subject can be served from cache without the authorization being re-evaluated, so stopping the lease is the part that has to happen first and does.

It does not touch serving manifests, generations or the parcel projection. Those are the data, not a cache of it, and re-creating them means re-fetching from LDG — which is a different decision from dropping a cache. Nobody is signed out: every subject whose lease is revoked simply re-authorizes on their next request.

There is no history on this screen: staffInvalidationsList is not registered, so an invalidation that ran an hour ago is not visible here and an empty screen is not evidence that none has run. The audit trail has them.

Invalidate

The affected leases and cached pages can be counted exactly for this scope.
One per line, or separated by commas.
Written to the audit record beside the counts. It is what another operator reads when they ask why a cache was dropped.
Revokes every lease across your whole reach, not only the scope named above.