Skip to content

Triggering Auto-Heal (Broadridge & FIS Global)

The AI story: Torch drives real app UIs, and when one changes it detects the drift, compares its own code to the live page with an LLM, and regenerates the broken selector. You demo it by breaking the app yourself from its hidden /dashboard.

Steps (both apps)

  1. Torch → connector → Settings → enable AI auto-healing.
  2. Open the app’s /dashboard, flip the drift toggle (below), Save.
  3. Run Enable Account on a test user → run fails in a few seconds.
  4. Wait ~10-15s → red drift banner appears on the Code tab.
  5. View AI-suggested fix → diff of old vs regenerated selector + explanation.
  6. Apply change → version bumps, banner clears. Re-run → succeeds.
  7. Reset: back to /dashboard, un-check the toggle, Save.

Broadridge

  • Dashboard: https://broadridge-web.demo.torch.security/dashboard
  • Toggle: Enable/Disable user: status dropdown variant — swaps the Enable/Disable buttons for a status dropdown.
  • Say: “Broadridge replaced its enable/disable buttons with a dropdown — Torch rewrote its own workflow to match, no engineer involved.”

FIS Global

  • Dashboard: https://fis-global-web.demo.torch.security/dashboard
  • Toggle: User-detail DOM drift — renames the user-detail container (user-detailuser-detail-v2).
  • Say: “FIS shipped a new user page and the structure changed — Torch detected the drift and regenerated the selector.”
  • Other toggles for side-stories: captcha, server outage, reject credentials, latency.

Watch (Torch UI)

Run fails (red) → Logs: element-not-found → Final DOM: the changed page → Code: drift banner → fix diff → Apply → version bump.