orcaLog in

Pipelines

mojo_issues

Progress

Runs at onceRuns of this pipeline going now, out of the most the scheduler starts at once (max_runs); the others wait in the queue. Fill runs come on top, up to fill_max_runs. Docs ↗
0 running of 1, 0 queued
Next runWhen the schedule fires next, in UTC, and the partition that run fills. Next runs, further down, lists the next five. Docs ↗
2026-11-11T08:00:00Z, fills 2026-11-11
CoverageHow much of the pipeline is done: its days or months done of those in its range so far (its first partition through the last that has ended), or a keyed pipeline's keys done of the keys its dataset has. Done means every step succeeded in a run of its current code, as on the calendar; failed, skipped, queued and running ones aren't. A dash means it has none to count yet. Docs ↗
— · The calendar

Runs

status any
last hourtoday24 h7 days

No runs.

All its runs

Versions docs

CommitThe git commit the binary was built from.ImageThe container image the code ran in, if any.CodeThe code hash: what the binary says about itself (its steps, partitions and schedule). It changes when they do, not on every build.First seenWhen a run first ran this version.Last seenThe last time it was seen.RunsHow many runs used it.
0df475ab1b3c of https://github.com/magmalake/mojo-census0x25d1c7ae61fde1c2026-11-11T04:18:06Z2026-11-11T04:18:06Z0