Oracle Integration Cloud: Building Integrations That Survive Production · Module 8 · Error handling, faults and retries
The four kinds of failure
Lesson 80 of 175 · 2 min
Four kinds of failure, and treating them alike is why so many integrations retry things that will never succeed. CONNECTIVITY: the target could not be reached. A network problem, an outage, a timeout. Transient by nature, so RETRY is the right response — with backoff, because retrying immediately against something that is down is Lesson 5's retry storm. AUTHORISATION: the target refused you. An expired credential, a revoked role, a certificate. PERMANENT until a human acts, so retrying is pure waste — it will fail identically a thousand times. The correct response is an alert. DATA: the payload is wrong. A missing required field, an unresolvable reference, a malformed value. Permanent for THIS record and irrelevant to the others, so the response is to set it aside and continue — a dead letter, not a retry and not a stop. BUSINESS RULE: the target understood you perfectly and said no.…
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