Console messages and states
A message in the Console names a state, not always a fault. This page maps the strings the Console displays to the condition behind each one and the action that clears it. Errors returned to a client by the gateway are a separate surface, catalogued in Gateway behavior.
How to read a Console state
Three rules cover most confusion:
- A Console message reflects stored configuration, not what the gateway is serving. A saved value is displayed as soon as it is stored, whether or not the data plane has received it. See Configuration propagation.
- An empty list is a state, not an error. Most empty states in the Console mean a prerequisite has not been completed, and they name it.
- A message about the data plane is usually about registration, not connectivity. Nothing in Agent Router connects inbound to a data plane, so a message about a missing data plane URL never means a connection is failing.
Data plane states
"DP is not yet configured"
A badge shown wherever the Console names the active data plane, with the hover text The administrator needs to complete the DP URL configuration.
| Means | No gateway address has been recorded for the data plane. It is not a connectivity check and does not mean a connection was attempted and failed |
| Triggered when | The organization has no data plane at all, or has one whose gateway URL is unset. Where several data planes exist, the badge appears against each entry missing a URL rather than across the whole selector |
| Cleared by | Registering the URL under System → Settings → Data planes, or by passing it at install time as tare install --serve-url. Either is sufficient |
| Who can clear it | An administrator. The message is shown to developers, who cannot act on it themselves |
The field this refers to is described in the onboarding wizard as the URL the management plane uses to reach the AI Gateway. That description is misleading and has been read as an inbound connection requirement. It is not one. What the value is actually used for, and why it does not need to be externally reachable, is set out in The Data plane URL field.
"Data Plane Not Configured"
The same condition as above, rendered as a full placeholder in the Playground with the message The administrator needs to complete the DP URL configuration. The Playground sends real traffic through the gateway, so it cannot open until a gateway address exists.
Playground placeholders
The Playground shows a placeholder rather than a prompt box until every prerequisite is met. Each names the missing one, and they are evaluated in this order, so the first unmet prerequisite is the one displayed.
| Title | Message | Condition | Action |
|---|---|---|---|
| Data Plane Not Configured | The administrator needs to complete the DP URL configuration. | No gateway URL is registered | Administrator registers the data plane URL |
| API Key Required | You need to create an API key to use Playground. | The account holds no API keys | Create one, from the placeholder's own button or from API Keys |
| API Key Required | Select an API key from the top bar to begin. | Keys exist, none is selected | Select a key in the top bar |
| Model Not Selected | Use the dropdown above to select a model. | No model is selected | Select a model. An empty dropdown is a separate condition, see below |
| Ready to Test | Select models, configure parameters, and click "Run Tests" to begin. | Everything is ready, in the comparison view | None. This is the ready state |
| Ready to Chat | Type a message below to start the conversation. | Everything is ready | None. This is the ready state |
An empty or short model list
The model dropdown offers what the selected API key can actually reach, which is not the same as what the organization has enabled. A key that reaches fewer models than the catalog shows is the normal appearance of a project grant, not a fault.
Enabling a model in the organization catalog makes it available to assign. It does not make it callable. The model and its provider must also be assigned to the project the key belongs to. This is the single most common cause of a working configuration that serves nothing, and it is covered in Add providers and models to projects.
To see what a key can reach without going through the Console, call GET /v1/models with that key. It returns exactly the routable set.
Provider and model states
| State | Means | Next step |
|---|---|---|
| A provider is enabled but no model behind it is callable | The provider most likely has no working credential. Agent Router Enterprise supplies no Tetrate-managed provider keys, so a credential is a day-one prerequisite rather than a cost optimization | Add providers and models to projects |
| A model is enabled in the catalog but a request returns 404 | The model is not assigned to the project the key belongs to | Create a project and grant models |
| A model expected on a key's Fallback or Traffic Splitting picker is not listed | Those pickers answer for the project the key belongs to, not the project the switcher is on. The model is not assigned to the key's project | Add providers and models to projects |
| A fallback or traffic-splitting save is rejected with an error naming a model | The policy names a model that is not assigned to the project the key belongs to | Add providers and models to projects |
| A model was enabled moments ago and is not yet callable | The change has not reached the data plane. The Console reads the catalog and shows it immediately; the gateway serves delivered configuration | Configuration propagation |
| The Console shows a provider as enabled while the data plane does not serve it | The same divergence, seen from the other side. It is expected briefly and worth investigating after a full sync interval | When a change has not taken effect |
The Console cannot be used to tell "applied" from "saved": it displays a stored value either way. A change is confirmed by sending a request through the gateway.
Announcement banners
Banners at the top of the Console with an information, warning, or critical style are operator-published announcements rather than system states. A critical announcement cannot be dismissed until an operator archives it. Publishing and archiving them is covered in Communicate with Agent Router users.
Related
- Gateway behavior: the error codes and bodies a client receives
- Configuration propagation: why the Console and the gateway can disagree
- Reading tare doctor output: the equivalent state reference for a self-hosted data plane