Git cursors
Data enters from git and nowhere else. A cursor advances only past work that is fully accounted for, so an interrupted batch replays.
| repository | last commit | last poll | imported | failed | last error |
|---|---|---|---|---|---|
| fs-test-results | 8f48bec1bd62 |
2026-10-06T15:55:46Z | 95 | 0 |
Import failures
None. A tarball that will not parse lands here instead of wedging the cursor.
Run cache
0 run(s), 0 bytes accounted, 0 hits / 0 misses. Run documents are immutable, so a cached one keyed on (_id, _rev) cannot go stale.