Oracle Integration Cloud: Building Integrations That Survive Production · Module 8 · Error handling, faults and retries
Scope and fault handlers
Lesson 82 of 175 · 2 min
Wrapping steps so a failure is caught WHERE YOU CAN DO SOMETHING ABOUT IT, rather than at the top where all context is gone. A scope groups steps and can carry its own fault handler. That is the mechanism, and the design question is where to draw the boundaries. DRAW THEM AROUND THINGS THAT FAIL FOR DIFFERENT REASONS AND NEED DIFFERENT RESPONSES. The lookup that might not find a match, the write that might be rejected, the delivery that might time out — three scopes, three handlers, three decisions. One scope around all three means one handler that cannot tell them apart. THE CONTEXT ARGUMENT IS THE WHOLE POINT. Inside a scope around one invoke you know which call failed, which record you were processing, and what you sent. At the top of the flow you know that something failed — and reconstructing the rest means reading the instance payload…
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