OIC: Getting AI Summaries for Failed Runs


Oracle Integration (Gen 3) can generate AI-powered error summaries for failed integration instances. On the Errors or Instances page, you expand a failed row to see a concise explanation and suggested fixes, with a link to the full activity stream for deeper forensics.


Prerequisites (one-time checks)

  • Oracle Integration 3 (Gen 3).
  • Region/availability: AI features appear in supported regions. If you don’t see the AI option on failed rows, review the AI feature availability page for your tenancy/region. AI Feature Availability


How to use AI summaries 
  • Inside a Project
    1. Go to Projects → open your project → Observe → Instances.
    2. Hover a row with Status = Errored.
    3. Click Expand to open the AI-powered error summary (it shows the probable cause and next actions).
    4. Use the activity stream link right under the suggestions to inspect the failing step and payload/logs.
  • From the global Observability area
    1. Click on Observability → Errors (or Instances).
    2. Hover an errored instance and expand to view the AI summary; jump to the activity stream from there. 
    3. Tip: On the Errors/Instances pages you can also download logs, filter only errors in the activity stream, and resubmit or discard failed messages—all from the same workspace.
  • Testing with an example
    1. Create a small REST-triggered integration that tries to call a non-existing or protected endpoint (e.g., a REST invoke that returns 401).
    2. Activate it and send a test request. It would fail.
    3. Open Observability → Errors (or the project’s Observe → Instances) and Expand the failed row to read the AI summary & suggested fixes(it highlights the failing action, likely root cause, and probable remedies).
    4. Click into the Activity Stream for payload details; adjust your connection/headers or mapping; resubmit from the Errors page. 






Good practices & guardrails

  • Use the AI hint, verify in logs. Treat the summary as guidance; always confirm in the activity stream and, if needed, download logs. 
  • Set right tracing level. You will still see AI summaries at Production tracing, but a richer context in the activity stream can improve diagnosis. (Raise tracing temporarily if you need deeper payload detail; before doing this ensure on PII/compliance.) 
  • Operationalize resubmits. Don’t discard messages you might need to resubmit as discarded items can’t be replayed.  

Comments

Popular posts from this blog

How Generative AI is Transforming Oracle Integration 3

Generative AI vs AI Agents vs Agentic AI: Understanding the Differences and When to Use Them

The Evolution of OpenAI’s GPT Models: From GPT-1 to GPT-5