Skip to content

Commit 361f40a

Browse files
docs(relay): scope Cloudflare's totals to tunnels past the grace periods
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent 129faa0 commit 361f40a

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

‎docs/operations/release.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -220,8 +220,8 @@ column in its first deploy with this change; the legacy switch stays `off` until
220220
2. Set the legacy mode to `dry-run`, deploy, and read `wouldDeleteLegacy`, `legacyOver30Days`,
221221
`totalDown`, and `totalInactive` on the sweep spans for a day. `wouldDeleteLegacy` counts only the
222222
tunnels a sweep inspected, at most 500 per status. `totalDown` and `totalInactive` are Cloudflare's
223-
counts of all idle tunnels in this stage, including ones the reaper skips, so they are an upper
224-
bound on the backlog. The share of `wouldDeleteLegacy` in each sweep's `scanned` estimates how
223+
counts of this stage's tunnels down for over five minutes and never connected for over an hour.
224+
They include ones the reaper skips, so they are an upper bound on the backlog. The share of `wouldDeleteLegacy` in each sweep's `scanned` estimates how
225225
much of that total is eligible.
226226
3. Run the legacy steps of the disposable-host canary below.
227227
4. Before enabling, confirm the web and mobile builds that show the "update T3 Code on that computer"

0 commit comments

Comments
 (0)