Oracle Integration Cloud: Building Integrations That Survive Production · Module 8 · Error handling, faults and retries
What to do with a caught fault
Lesson 83 of 175 · 2 min
Four options — retry, skip, route aside, stop — and choosing PER FAILURE KIND rather than picking one for the whole integration. RETRY, for connectivity. The target was unreachable and may be reachable in a minute. With backoff and a cap, per Lesson 5. SKIP, for a record whose failure does not affect the others. Log it, continue, and report at the end. This is the right default in a batch, because the alternative — stopping — lets one bad record block four hundred good ones. ROUTE ASIDE, for a record that needs human attention. The dead letter of Lesson 6: somewhere durable, with enough context to be actionable, that somebody actually reads. STOP, for a failure that makes everything after it meaningless. An expired credential, a target that is refusing everything, a configuration problem. Continuing through four hundred identical authorisation failures is worse than stopping at the first, because…
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