Troubleshooting
The model does not appear in /v1/models
Section titled “The model does not appear in /v1/models”Use the full <namespace>/<code> model ID, deploy after creating or editing the model, and ensure the API key allows that model or namespace.
The runtime returns an authentication error
Section titled “The runtime returns an authentication error”Use a current runtime API key as a Bearer token. Provider API keys authenticate the workspace to upstream providers; they are not client runtime keys.
The model cannot reach its provider
Section titled “The model cannot reach its provider”Check that the target starts with the configured provider code and that its base URL, protocol style, and credential are correct. Saving a provider change still requires deployment.
A tool is never called
Section titled “A tool is never called”Confirm the tool is attached to the target model, saved, and deployed. Improve its description, argument schema, and prompt fragment so the model knows when to use it. Do not manually add a second tool-loop wrapper to the model source.
The custom domain is pending
Section titled “The custom domain is pending”Copy the CNAME and any TXT records exactly as shown in the dashboard. Wait for DNS propagation, then use Check status. Read any verification errors shown there before changing the connection.