orcaLog in

Pipelines

gharchive_index paused

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
CoverageWhich days or months a run has done, failed or not reached yet, as a calendar on the Operate tab. Docs ↗
The calendar

Coverage

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

0 done · 0 failed · 0 running or queued · 30 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.

Same from the command line (on the control instance today, remotely once #111 lands):

orca backfill gharchive_index <range>
/opt/orca/pipelines/gharchive_index run --partitions <range>

The second runs in that shell's process rather than queuing it; orca has no command that queues one run. The scheduler (orca scheduler) starts queued runs, up to 1 at once.

Stop runs

Cancelling stops runs that are queued or waiting to be retried, and asks running ones to stop before their next step. Paused: the scheduler starts none of its runs; fires, sensors, retries and backfills queue theirs until it's unpaused.