orcaLog in

Pipelines

gharchive

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
FillWith fills = "all" in orca.toml the scheduler works through the whole range by itself, one partition per fill run, within a daily budget and a window. This is how far it got, how fast, and what it spent today. Docs ↗
1408 / 1408 done (100%); today $0.00, no budget (estimated)
Idle: complete
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-10T03:00:00Z, fills 2026-11-09
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 ↗
1408 / 1408 days done (100%)

Coverage

MonthYear
April 2023
  • 1, 2023-04-01 done
  • 2, 2023-04-02 done
  • 3, 2023-04-03 done
  • 4, 2023-04-04 done
  • 5, 2023-04-05 done
  • 6, 2023-04-06 done
  • 7, 2023-04-07 done
  • 8, 2023-04-08 done
  • 9, 2023-04-09 done
  • 10, 2023-04-10 done
  • 11, 2023-04-11 done
  • 12, 2023-04-12 done
  • 13, 2023-04-13 done
  • 14, 2023-04-14 done
  • 15, 2023-04-15 done
  • 16, 2023-04-16 done
  • 17, 2023-04-17 done
  • 18, 2023-04-18 done
  • 19, 2023-04-19 done
  • 20, 2023-04-20 done
  • 21, 2023-04-21 done
  • 22, 2023-04-22 done
  • 23, 2023-04-23 done
  • 24, 2023-04-24 done
  • 25, 2023-04-25 done
  • 26, 2023-04-26 done
  • 27, 2023-04-27 done
  • 28, 2023-04-28 done
  • 29, 2023-04-29 done
  • 30, 2023-04-30 done

30 done · 0 failed · 0 running or queued · 0 not run · 0 outside the pipeline's range

Start runs docs

Queues a run for each day in the range that hasn't succeeded and isn't in a queued or running run.

Queues a single run over every day in the range, done or not; refused while a queued or running run has one of them.

From the command line:

orca login <url> && orca --remote <url> backfill gharchive <range>

Stop runs

Cancelling stops runs that are queued or waiting to be retried, and asks running ones to stop before their next step. Pausing stops the scheduler starting its runs, which stay queued; runs already going go on.