Oracle Integration Cloud: Building Integrations That Survive Production · Module 8 · Error handling, faults and retries
What breaks: five error-handling failures
Lesson 91 of 175 · 2 min
Five error-handling failures, and each is a habit rather than a bug. ONE: A RETRY ON A PERMANENT ERROR. An expired credential retried five times an hour for a week. Load, noise, and a queue full of one problem — and the alert that would have named it fired on attempt one and was lost among the rest. Lesson 1. TWO: A FAULT HANDLER THAT SWALLOWED THE CAUSE. A handler that catches, logs "an error occurred", and continues. The instance shows a failure with no diagnosis, and the information the target sent — which named the field and the constraint — was discarded by your own code. Always log what the target actually said. THREE: A DEAD LETTER NOBODY READ. Six months of failures in a table, and a business that has been missing records without knowing. Lesson 6. FOUR: AN ALERT ON EVERY RECORD. Four hundred emails, a filter…
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