Oracle Integration Cloud: Building Integrations That Survive Production · Module 13 · Monitoring, tracking and alerting
Errors versus rejections in the console
Lesson 131 of 175 · 2 min
Distinguishing an INCIDENT from a BUSINESS REJECTION, so the queue you watch stays the one that needs a human. This is Module 8's distinction arriving in the console, and it decides whether monitoring is usable at all. AN ERROR IS SOMETHING WRONG WITH THE INTEGRATION OR ITS ENVIRONMENT — a system unreachable, a credential refused, a mapping that produced something the target could not parse. It should be retried or fixed, and somebody needs to know. A REJECTION IS THE TARGET WORKING CORRECTLY. The invoice references a closed period. The supplier does not exist. The amount fails a validation rule. Nothing is broken; a business record cannot be created and a business person needs to decide what to do about it. COLLAPSE THE TWO AND THE QUEUE BECOMES UNREADABLE IN BOTH DIRECTIONS. If rejections are recorded as failures, the failed list fills with items nobody technical can act on, and…
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 13 · Monitoring, tracking and alerting
- 1The monitoring console
- 2Tracking variables: the one design decisionFree preview
- 3Reading a failed instance
- 4Payload retention, and its limits
- 5Errors versus rejections in the console
- 6Alerting: who, when, how loud
- 7The silent failure: nothing ran
- 8Reporting to the business
- 9What breaks: the integration nobody knew had stopped
- 10Lab briefing · Make a failure visible in five minutes