Backfills
An evaluation only grades data captured after you create it. A backfill runs it over traffic you already have, up to 30 days back, so a new evaluation shows you how quality changed before it existed.
Start a backfill from the Backfills tab on any evaluation. It covers whatever the evaluation targets: generations, traces, or sessions.
Backfills use your existing live data. To test changes before they reach production, use offline evals instead.
How backfills work
A backfill runs the evaluation over a time range you pick. It starts from the evaluation's own property filters and sampling rate, and you can change either one for this run without touching the evaluation itself. Whatever you pick is frozen on the backfill, so later edits to the evaluation do not change what a run already covered.
By default it skips anything the evaluation has already graded, so a run over a range the evaluation was already covering finds nothing to do. To grade that data again, turn on Include generations that already have a result. See Re-evaluating generations that already have a result.
Results appear alongside live results in the evaluation's run history, and each backfill row links to the results it produced.
Creating a backfill
- Open the evaluation and go to the Backfills tab
- Pick a time range, up to 30 days back
- Open Conditions to change the property filters or sampling rate for this run, or leave them as the evaluation has them
- Check the count above the Start backfill button, which shows how much would be evaluated
- Click Start backfill and confirm
One backfill runs at a time per evaluation. You can cancel a run while it is in progress, and results it already saved stay.
Re-evaluating generations that already have a result
Turn on Include generations that already have a result to grade the same data a second time. Use it after changing a prompt or a code check, when you want the new version applied to data the old version already scored. Both results are kept, so you can compare them on the trace or session they graded.
Reading backfill progress
The Covered column counts how much of the range holds a result. A finished backfill usually reads as fully covered, because the evaluation grades new data on its own while the backfill works through older data.
Expand a row to see the range, the conditions it used, and how much it started, skipped, or left without a result.
When the count is zero
An enabled evaluation covers its own traffic within minutes, so a range it has been running over has nothing left to grade, and the count reads zero. This is expected, not an error. To grade that range again, turn on Include generations that already have a result.
The most recent few minutes are also held back, because an evaluation waits for a generation to settle before grading it.
A Whole session evaluation also reads zero when your generations don't carry $ai_session_id, because there are no sessions to grade. Including results that already exist doesn't change that count. See Choosing what to evaluate.
Backfill pricing
Every generation, trace, or session a backfill evaluates counts as one AI Observability event, the same as a live evaluation, and LLM judge backfills use your provider API key. The confirmation dialog shows how much will be evaluated before you start, so check that number on a wide range.





