A daily ingestion job may be retried after a network interruption. Which write design best prevents duplicate records?

1. Generate a new random key for every retry of every row
2. Use the run's display title as the only deduplication logic
3. Ignore all successful writes after a timeout
4. Stable business keys with idempotent upsert or equivalent reconciliation