Scenario 11: sso-identity-provider — Self-Correcting RCA

The standout scenario: a wrong RCA gets approved, the fix makes things worse, and a second run corrects it automatically.

SSO and MFA logins are failing. The AI's top-ranked hypothesis (network packet loss) is plausible but wrong; the real cause — an expired SAML signing certificate — is ranked #2 and gets missed.

Steps to test

  1. Open INC0000011.
  2. Run 1 — steps 10–11: top hypothesis (network packet loss) at 0.63 confidence; the real cause is ranked #2 at 0.29.
  3. Step 12: reviewer approves the wrong hypothesis.
  4. Steps 13–14: network failover executed live — verification outcome REGRESSION, login errors rise from 35% to 52%.
  5. Run 2, auto-triggered by the failed verification, correctly ranks the SAML cert expiry at 0.81 confidence and is approved.
  6. Above the summary, use the run comparison bar to compare run 2 with run 1 — new hypotheses and changed confidence are called out.
  7. Step 11: in the evidence graph, find the edge labelled "supersedes" linking run 1's root cause to run 2's.
  8. Step 13: run 2's corrected fix — renew the SAML signing certificate — is waiting for remediation approval; step 14 still shows run 1's failed network failover and its REGRESSION verdict.
Outcome: the platform's full self-correction loop, end to end — try approving run 2's remediation plan yourself.