Pipeline Activity

Pipeline Activity reports the state of Statsig Warehouse Native pipeline runs: which runs are executing right now, which recent runs succeeded or failed, how long each one took, and the SQL each job sent to your warehouse. Open it at Data > Pipeline Activity in the Statsig Console when a reload looks stuck, a Pulse result looks stale, or you want to know what the pipeline has been running in your warehouse over the last two weeks.

Use Pipeline Activity for run status across every experiment and gate in the project. Use Pipeline Overview instead when you want to understand the pipeline itself: the stages it runs, the tables it writes into your warehouse, and the metric source and dashboard Statsig provisions for it. For the exposure and metric health of a single experiment, go to Experiment Diagnostics.

Pipeline Activity covers warehouse-native projects. Projects that don't run a Statsig Warehouse Native pipeline have nothing to report, so the page doesn't apply to them.

What the job list shows

The job list holds one row per pipeline run.

Filter the job list

Four controls narrow the list:

• Run state: every run, or only the runs that are still active.
• Status: Success, Failed, Partial failure, or Cancelled.
• Entity: a single experiment or feature gate. This filter covers experiments and gates only.
• Started by: the person or process that triggered the run.

Changing any filter returns the list to the first page. The completed-runs list holds 25 runs per page.

Read the job runtime chart

A stacked bar chart sits at the top of the page and plots daily job runtime grouped by job type. The chart breaks out the largest job types and collects the rest into Other. It covers the last 14 days by default, accepts a range of up to 30 days, and excludes today.

Three things shape how the bars add up:

• Each bar sums the durations of the jobs that ran that day. Jobs inside a run execute in parallel, so a single day's bar can total more than 24 hours. Read a bar as total job effort, not as elapsed time.
• Statsig attributes a run to the day it created the run, in your browser's timezone. A run that starts before midnight and finishes after it counts entirely on its start day.
• Where a job has no recorded runtime, Statsig falls back to an estimate, so a bar can mix measured and estimated values.

The chart range and the job list filters work independently. Changing the range doesn't filter the table, and filtering the table doesn't redraw the chart.

Inspect a run

1. Find the run in the job list.
2. Click View details.
3. Select a view in the dialog that opens:
   • SQL: the queries the run sent to your warehouse.
   • Details: the run's metadata.
   • DAG: the job graph for the run.
   • Timeline: when each job in the run started and finished.

The DAG and Timeline views appear only for runs that carry that data. From either one, click a job to jump straight to that job's SQL.

Cancel an active run

1. Narrow the job list to active runs.
2. Find the run you want to stop.
3. In the Actions column, click Cancel.

The job list doesn't poll for status changes. Only the elapsed-time clock advances on its own, so refresh the page or change a filter to pull current status, including after you cancel a run.

Limitations