Tolerant recovery

Recovery happens at physical-line boundaries. A malformed line, invalid prop, unknown component, or unresolved reference produces a diagnostic and can be dropped while later independent statements continue.

root = Answer(children=[title, body])
title = Heading(text="Recovered answer", level=1)
broken = Text(text="This line never closes"
body = RichText(format="markdown", text="Later **valid** content survives.")

Recovery is deliberately bounded. It does not reinterpret arbitrary text, loosen a JSON Schema, enable an unknown action, or commit a graph with a missing root, unresolved reachable reference, cycle, or exceeded resource budget.

Terminal failures

Use a trusted fallback and observe typed diagnostics:

<RUIRenderer
  streamStatus={status}
  fallback={({ diagnostics, status }) => (
    <FallbackView state={status} diagnosticCount={diagnostics.length} />
  )}
  onError={(event) => logDiagnosticCodes(event)}
>
  {source}
</RUIRenderer>

Do not display raw provider errors, prompts, credentials, or sensitive source in a fallback. To retry from a clean compiler state, increment retryKey and begin with the new attempt’s accumulated source. See the language specification for exact grammar and commit rules.

Accumulated streaming Catalog and registry

⌘I

Get started

Render content

Configure Rixx UI

Frameworks and tools

Security

API reference

Architecture

Project

Tolerant recovery

Terminal failures

​Terminal failures

Terminal failures