Skip to main content
ENES
Bring a workflow →

The agent's model is not available

Symptom​

When you open or save an agent, one of these warnings appears:

  • "El modelo guardado (nombre del modelo) ya no está disponible para este Agent. Elige un modelo compatible." (The saved model (nombre del modelo) is no longer available for this Agent. Choose a compatible model.)
  • "El modelo seleccionado no tiene proveedor asociado. Selecciónalo desde el catálogo para guardar." (The selected model has no associated provider. Select it from the catalog to save.)
  • "No se pudo conectar con el nodo de inferencia." (Could not connect to the inference node.) or "No se pudo actualizar desde el nodo de inferencia. Mostrando el último catálogo disponible." (Could not refresh from the inference node. Showing the last available catalog.)

The agent may appear as Requiere atención (Needs attention) in the list.

Cause​

  • The model was removed from the Catalog or its activation was stopped (Detener (Stop) on the model's card), and the agent had it saved.
  • The model belongs to an external provider whose credential was deleted or whose provider is no longer enabled for the Client.
  • InferNode is not responding at that moment; Studio shows the last catalog it knew.

How to confirm it​

An administrator opens Infraestructura > Catálogo (Infrastructure > Catalog) and looks for the model: if it is not there or does not say Activo (Active), it is the first cause. In Administración > Credenciales (Administration > Credentials), if the model's provider does not appear or is Sin configurar (Not configured), it is the second. If the Dashboard shows "Panel inicializándose" (Dashboard initializing) or "Snapshot antiguo" (Stale snapshot), it is the third (The Dashboard shows no data).

Solution​

  1. Open the agent's model selector and choose an Activo model from the Catalog; save. The status goes back to Publicado (Published).
  2. If the model was external and you need it, the administrator restores the credential (Shared credentials).
  3. If InferNode is the one not responding, wait a few minutes; if it persists, the administrator reports it to the operator.

Workflows that use that agent inherit the problem: check Todos los flujos (All workflows) and publish changes after the fix (A published workflow ends up in Requiere atención).

Next step​

Last updated on