Oracle Integration Cloud: Building Integrations That Survive Production · Module 8 · Error handling, faults and retries
Lab briefing · Break it five ways
Lesson 92 of 175 · 2 min
Take the working flow from Module 6 and engineer FIVE failures — one of each kind — then handle each appropriately and PROVE the handling. The five, and each has a specific correct response. CONNECTIVITY: point an invoke at an unreachable endpoint. Expect a retry with backoff, then an alert. AUTHORISATION: break the credential. Expect NO retry — an immediate alert and a stop. DATA: put a malformed record in the file. Expect the record aside and the run continuing. BUSINESS RULE: submit something the target legitimately refuses. Expect it recorded as an outcome, not an incident. AND A FLOW ERROR: a null where an expression expects a value. PROVING THE HANDLING IS THE GRADED PART, and it means answering three questions per failure. Did the run do what you intended? Can you tell WHICH record failed, from the instance alone? And was somebody told — once, with enough detail…
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 8 · Error handling, faults and retries
- 1The four kinds of failure
- 2Faults versus errorsFree preview
- 3Scope and fault handlers
- 4What to do with a caught fault
- 5Retry: how many, how far apart
- 6The dead letter, and who reads it
- 7Partial failure in a batch
- 8Compensation, and its limits
- 9Alerting a human
- 10Resubmission: doing it safely
- 11Errors that are not failures
- 12What breaks: five error-handling failures
- 13Lab briefing · Break it five ways