Does ngrok's offset‑based pagination remain stable when inspection data is purged mid‑scan?

When using ngrok’s inspection API to page through request logs, clients typically combine a fixed limit with an increasing offset to retrieve successive batches. Ngrok automatically removes older inspection entries after a configurable retention period, which can change the total number of stored requests while a pagination walk is in progress.

This raises uncertainty about whether the offset‑based approach guarantees non‑overlapping, gap‑free pages when the underlying dataset may shrink between requests. Understanding the exact behavior helps decide if additional client‑side checks are needed.

Does specifying a fixed limit and incrementing offset by the previous limit still produce distinct, consecutive pages if ngrok purges entries during the walk?

What does the API return when an offset points to data that has already been deleted?

Should clients rely on the actual count returned in each page to compute the next offset instead of a fixed increment?