Skip to main content
Cascading configuration defines the requested backup models when a primary model cannot provide an acceptable response in time. Saving that policy is separate from demonstrating failover in a live conversation.

​
Select the policy

The dashboard’s Backup LLM configuration provides Default, Custom, and Disabled choices. These map to conversation_config.agent.prompt.backup_llm_config: cascade_timeout_seconds defaults to 4 seconds and accepts 2–15 seconds. Review model compatibility, latency requirements, and provider costs before changing the order or timeout.

​
Review and save

Use platform-managed backup discovery and the LLM catalog. Preserve the selected primary model and unrelated prompt settings. For supported managed text-only publication, the primary and backups must resolve against the same catalog release. Read the saved branch or draft back. Empty or incompatible custom backup selections, or an unavailable default policy, can prevent publication. Custom LLM selection requires disabled backups and cannot currently be published.

​
Frequently asked questions

No. It records fallback intent. End-to-end latency and actual failover require a released runtime and measured tests.
The reviewed custom-LLM selection requires disabled backups. Do not substitute custom endpoint definitions for supported catalog IDs.