Table Actions and Handoffs

The result table is the control surface for most ZeroTrace Proxy workflows. It is where you turn a big result set into the next precise action. Search narrows the set, sorting ranks it, column visibility removes noise, row selection captures intent, and handoffs move only the rows you actually want to the next tool.

Do not think of the table as a passive report. Treat it like a staging area.

Build A Review View

Start by hiding columns you do not need. For checker triage, you might keep status, protocol, HTTPS support, quality, anonymity, latency, country, network type, ASN, ISP, and error. For benchmark review, you might keep success rate, pass count, average latency, best latency, worst latency, HTTPS support, and last error.

Then sort the table around the decision you are making. If you are looking for speed, sort latency. If you are cleaning a pool, sort status and failure details. If you are preparing a rotator source, sort success rate and worst latency so unstable rows are harder to miss.

Select, Visible, Or Ready

ZeroTrace Proxy uses three handoff styles because not every decision is the same:

For most workflows, visible rows are the sweet spot. They make the filter part of the decision. If you filter to alive, HTTPS-capable, high-score rows and then hand off visible rows, the next task inherits exactly the group you reviewed.

Common Handoffs

Extractor results usually go to Checker. Checker results split into Benchmark, Leak Test, Proxy Viewer, or Pools. Benchmark winners often go to Leak Test, then into a final pool. Chain Tester winners go to Chain Engine. Leak Test clean rows go to a pool or export.

If a handoff reports skipped rows, do not immediately retry the same thing. Look at the skipped rows. They may be missing a normalized proxy value, they may be dead, or they may belong in a different destination tool.