Server‑Side LIST pagination: when does a continue token expire?

Server‑Side LIST pagination: when does a continue token expire?

When exporting a large set of objects with the API server’s LIST chunking, clients supply limit and receive a continue token in metadata.continue. The next call repeats the query with that token. In practice, the token is tied to a snapshot resourceVersion, and if the snapshot becomes stale or the underlying data changes, the server may return 410 Gone or ResourceExpired. This behavior is documented but not fully exposed in client examples, leaving teams uncertain about how long a token remains valid or what triggers expiration.

Key uncertainties include:

1. What specific conditions cause the API server to reject a continue token?
2. Is there a documented timeout or resourceVersion mismatch that triggers a 410 Gone?
3. When a token is invalid, should a client restart the LIST from the beginning or attempt a fallback strategy?