Data Sketch
Back to gallery

Episode 07 / Pipelines

Late-Arriving Data

Data can reach a pipeline after the period it belongs to. Historical edits, backdated transactions, batch uploads, network lag, and delayed source systems are five causes to check.

Five causes of late-arriving data: historical edits, backdated transactions, batch delays, network lag, and source delays

Reading the sketch

  1. Updated historical records

    A source can modify a record after the pipeline has already processed its original value.

  2. Backdated transactions

    A newly entered transaction can carry an older business date.

  3. Batch upload delays

    A source may hold records until its next batch upload or processing run.

  4. API or network lag

    Slow transmission can delay when records become available to the pipeline.

  5. Delayed source systems

    A source can deliver data after the downstream pipeline has already run.

View the original LinkedIn post (opens in a new tab)