Processing history

Every run, and what became of it.

Each archive dropped into the pipeline becomes a run. This page lists the runs Edgent has processed, newest first: what kind each was, whether it finished, how many pages were read and how many failed, and the source archive it came from.

This reads the same governed record the pipeline writes. It runs server-side, inside Edgent's boundary; nothing is computed in your browser. Every read and write behind these runs lands in the tamper-evident audit trail, and each run's per-page timing waterfall opens right here under View timing.