# Backfill the window a failed job skipped

A gap left by a failed job, filled with counts reconciled and the rerun proven idempotent.

Category: Pipelines and warehouse
Source: https://letsship.ai/use-cases/backfill-a-skipped-window
Published: 2026-08-25

## Goal

Backfill the window a failed job skipped and reconcile the result.

## Acceptance criteria

- The gap is identified precisely before anything runs
- Row counts are reconciled against the source
- Running the backfill twice does not duplicate rows
- Downstream models are refreshed after the backfill

## What lands as proof

Reconciled counts against the source, plus a demonstration that a second run changes nothing.

## Prompt

Copy this to an agent to open the ticket:

```text
Create a Linear issue in my team and assign it to the SHIP agent.

Title: Backfill {window} for {table}

Description: Backfill the window a failed job skipped and reconcile the result.

Acceptance criteria:
- The gap is identified precisely before anything runs
- Row counts are reconciled against the source
- Running the backfill twice does not duplicate rows
- Downstream models are refreshed after the backfill

Before you create the issue, identify the exact missing window in this repository's warehouse and replace {window} and {table}.
```

## Questions

### What does the agent actually change?

The ticket is scoped to one outcome: backfill the window a failed job skipped and reconcile the result. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.

### How do I know the work is done?

The pull request carries the evidence, not only the diff. Here that means row counts before and after, the rerun proven idempotent, so a reviewer can confirm the result without reproducing the work locally.

### How much oversight does this need?

The run stops for the plan, and the review bar is raised afterwards so that smaller suggestions block the merge too, not only serious findings.