Freshness of the application list

The Lifecycle

Transitions Explained

Current and aging are timing categories derived from the provider timestamp, not persisted states or proof of current authority. Refusal can request refresh immediately. Focus or visibility requests it only when the tab is visible and the timestamp is at least five minutes old.

What Cannot Happen

A refresh result cannot replace applications after its workspace ticket is superseded. Without a selected workspace, the refresh function returns without a request. Failure does not make an aged timestamp recent.

Concurrency and Timing

One promise is shared across concurrent callers, including callers in different workspaces. Successful response arrival advances the timestamp before the ticket check; failure leaves it unchanged. Boot and entry do not reset it. The service response can still reflect authorizer-cached licensing data.