Data Monitoring / Pipeline Freshness & Data Quality
Data pipelines: Idempotent retries
A failed task rerun creates a second copy of already written rows. Compare retry attempt identifiers with target business keys and commit boundaries.
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 failed task rerun creates a second copy of already written rows. Confirm the cause before choosing a fix.
Evidence to collect
Compare retry attempt identifiers with target business keys and commit boundaries. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Use an idempotent write strategy and test failure after partial progress. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for idempotent retries 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.