What breaks: four file failures

Four file failures, and three of them produce successful runs. ONE: A HALF-WRITTEN FILE READ MID-UPLOAD. The partner is still writing; your pattern matched; you processed part of a file. The run succeeds, the records are real, and the missing ones are missing silently — and the file is now in your processed directory, so the rest never arrives. Marker files, Lesson 7. TWO: A FILE PROCESSED TWICE AFTER A RESTART. The run died, the file was still in inbound, the next run read it again. Whatever the first run committed is committed twice, and for anything transactional that is a duplicate nobody sees until a reconciliation. Lesson 4's move-first ordering. THREE: AN ENCODING THAT CORRUPTED ARABIC NAMES. The file was read in the wrong encoding and the names became something else. The load succeeded and the records are wrong — visibly wrong, to anybody who reads them, and invisible…

In this module: Module 7 · Scheduled integrations and file handling

1. 1Scheduling an integration
2. 2Parameters and run state
3. 3Reading files: patterns and directories
4. 4The staging problem
5. 5Large files and chunking
6. 6Writing files a partner can read
7. 7Archiving and idempotent file processing
8. 8Catching the file that never arrived
9. 9What breaks: four file failures
10. 10Lab briefing · A nightly file, done properly