Skip to content

Traffic: Model unavailable and Not routed for requests sent nowhere - #363

Merged
fylorn merged 1 commit into
devfrom
feat/traffic-model-refused
Oct 22, 2026
Merged

fylorn merged 1 commit into
devfrom
feat/traffic-model-refused

Conversation

@fylorn

@fylorn fylorn commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Core now records requests that are refused before reaching any upstream (ThinkWatchProject/ThinkWatch-Core#366): a model name that does not exist, is not allowed for the key, or whose alias or specified model does not resolve, plus requests no rule decided on and requests made before any upstream is configured. Until now the Traffic page would have shown all of these as "No upstream".

  • gw.model.* (except gw.model.no_upstream_available, which stays "No upstream") and gw.ws.alias_unserved* show as Model unavailable, with a crossed-out magnifier in the upstream column.
  • gw.route.failed and gw.config.no_upstreams show as Not routed.
  • The request drawer's Routing tab gives a sentence for each, and the reason line shows core's message (which names the model and why it cannot be used).

These rows appear once Lite pins a core release that includes #366; until then nothing changes.

Refs #356

🤖 Generated with Claude Code

…heir own kinds

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fylorn
fylorn merged commit 8dffe11 into dev Oct 22, 2026
6 checks passed
@fylorn
fylorn deleted the feat/traffic-model-refused branch October 22, 2026 13:07
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 22, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant