Data Monitoring / Pipeline Freshness & Data Quality
Data pipelines: Late data watermark policy
A completed dashboard period changes as late records arrive. Measure lateness distribution and identify the current completion watermark.
Environment and inputs: Data pipelines and analytical datasets; Apache Airflow is an orchestration example. Quality acceptance rules must match the dataset contract.
Failure scenario
A completed dashboard period changes as late records arrive. Confirm the cause before choosing a fix.
Evidence to collect
Measure lateness distribution and identify the current completion watermark. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Publish the provisional or final status of periods and choose a justified lateness allowance. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for late data watermark policy using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.