> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Proxy errors

> Diagnose authentication, entity, routing, provider, and upstream failures.

Proxy-generated errors use this shape:

```json theme={"system"}
{
  "error": {
    "message": "No task 'ticket-classifier' in entity 'personal-user'. Did you mean to pass metadata[\"wandb.entity\"]?",
    "type": "proxy_error"
  }
}
```

Every response includes `x-proxy-request-id`. Include it when reporting a problem.

## Common failures

| Status          | Typical cause                                                                | Action                                                                   |
| --------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| 400             | Missing model, invalid metadata, unsafe trace destination, or malformed JSON | Correct the request body                                                 |
| 401             | Missing or invalid W\&B bearer key                                           | Use a current W\&B API key                                               |
| 403             | The key cannot access the requested entity                                   | Change `wandb.entity` or grant team access                               |
| 404             | Unknown task/version/provider or unsupported path                            | Check entity, alias, version, and provider deployment                    |
| 502             | Provider could not be reached or its response stream failed                  | Inspect provider availability and credentials                            |
| Provider status | The selected provider returned an error                                      | Read the provider response; the proxy preserves upstream status and body |

## The most common entity mistake

A personal W\&B key defaults to its personal entity. A team task therefore needs:

```json theme={"system"}
{"metadata": {"wandb.entity": "team-name"}}
```

## A model ID error is not a proxy 404

The proxy validates the provider name, not every upstream model ID. If the provider exists but the model does not, the selected provider returns its own error. This distinction helps separate routing configuration from provider catalog drift.

## Tracing failures

Trace writes are asynchronous and do not turn a successful provider response into a client failure. Operators monitor structured write-failure events with the same proxy request ID. Deterministic trace-input problems are rejected before provider dispatch when possible.

<Accordion title="API: Diagnose a failure">
  Provide the agent with the request URL, redacted request body, HTTP status, full response body, and `x-proxy-request-id`. Do not share the bearer key or provider credential.

  An agent should check, in order:

  1. the selected entity in `metadata["wandb.entity"]`;
  2. whether `model` is a task alias, pinned task version, or registered provider reference;
  3. whether the provider and routing deployment are applied;
  4. whether the response body came from the proxy or the upstream provider.

  The machine-readable error schema is in the [Inference proxy OpenAPI specification](/openapi/model-distillation/proxy.openapi.yaml).
</Accordion>