Skip to content
Blog
Zild AdminZild updates

ModelOps: catalog and per-model fallback

Choose the models enabled for your company and configure an alternative for temporary provider failures.

Prepared on Oct 28, 2026 · 1 min

Change identified in code:

Feature identified in the platform code in October 2026. Availability depends on the deployed version, permissions and environment connectors. Contact Zild if it is not visible yet.

What changed

Choose the models enabled for your company and configure an alternative for temporary provider failures.

How to use it

In Admin ModelOps, enable the required models and assign each fallback. Configure both provider connectors and validate the tools, images and structured outputs required by the agent. The fallback must also be enabled in the company catalog.

Limits and prerequisites

Temporary failures such as 429 and 5xx trigger one fallback attempt. Authorization, validation and tool errors do not trigger switching. Provider-bound resources such as VectorStoreId may prevent cross-provider switching. External voice platforms do not use this fallback.

Validate in your operation

Test the alternative in staging and inspect the actual model, attempts and cost. Switching does not change the agent's saved model. A company without its own configuration does not automatically receive the global catalog.

Retrospective edition 2026-W30. The week identifies this collection’s editorial organization; the text was prepared on the date shown above.

Bring this idea into your operations.

Map the process, connect systems and evaluate outcomes with Zild.

Talk to an expert