Oracle Integration Cloud: Building Integrations That Survive Production · Module 7 · Scheduled integrations and file handling
Catching the file that never arrived
Lesson 77 of 175 · 2 min
A MISSING FILE PRODUCES NO ERROR, BECAUSE NOTHING RAN. That sentence is the whole lesson and it is the commonest silent failure in file integration. The schedule fires, the pattern matches nothing, the run completes successfully having processed zero files. Monitoring is green. The receiving system got nothing. And nothing anywhere is wrong, as far as any component can tell — because "no files today" is a legitimate outcome. THE CHECK THAT TURNS SILENCE INTO AN ALERT is an expectation. Somebody has to say "a file arrives every weekday by 6am", and something has to compare reality against that. The pattern that works: a separate scheduled check, running after the expected arrival window, that asks whether a file was processed in the period and alerts if not. It is a small integration and it is the most valuable one in this module, because the flow it watches cannot detect its…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.
In this module: Module 7 · Scheduled integrations and file handling
- 1Scheduling an integration
- 2Parameters and run state
- 3Reading files: patterns and directories
- 4The staging problem
- 5Large files and chunking
- 6Writing files a partner can read
- 7Archiving and idempotent file processing
- 8Catching the file that never arrived
- 9What breaks: four file failures
- 10Lab briefing · A nightly file, done properly