Oracle Integration Cloud: Building Integrations That Survive Production · Module 8 · Error handling, faults and retries
Resubmission: doing it safely
Lesson 89 of 175 · 2 min
Reprocessing a failed instance from the console. What it re-runs, what it does not, and the check to do first. A resubmission runs the flow again with the original message. That is the whole mechanism and it is exactly as dangerous as it sounds: the flow does not know it has run before, so everything it did the first time it will attempt again. WHAT IT RE-RUNS: everything from the beginning. Not from the point of failure. So an instance that failed at step six re-executes steps one to five — including any writes they made. WHAT IT DOES NOT DO: undo anything. The records the first run created still exist. SO THE CHECK TO DO FIRST IS: WHAT DID THE FAILED RUN ALREADY COMMIT? Open the instance, read the steps that succeeded, and count what landed in the target. Resubmitting a flow that posted 199 of 400 records without…
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