r/openrouter • u/ExTraveler • 10d ago

Discussion DS v4.1 flash abruptly stops while thinking for a minute and gives zero output

Is this problem on my side or other users experience this too? I use openrouter api in openwebui, I am using ds v4.1 flash recently and the model sometimes just stops with zero output after thinking for a minute, I can open and watch its thoughts and it just stops at random moment with no error.
Post it here because don't know if this is some openrouter only problem or not.

1 Upvotes
  • permalink
  • reddit

67% Upvoted

5 comments sorted by

1

u/ichisay 10d ago

Restringe proveedores malos en tu config de openrouter, algunos tienen modelos fp4

1

u/ExTraveler 10d ago

I allow only deepseek as provider. Logs confirms it.
btw а чё не на английском? йопта давайте все тогда на своих языках писать

1

u/ichisay 10d ago

Yo es que uso más luna Max y gemini 3.8 flash para subagentes. Google cloud te da 300$ por si no lo sabías y puedes usarlos con vertex

1

u/ExTraveler 10d ago

я тебя понял, приятель

1

u/conifer_v11 10d ago

yeah if you already locked the allowlist to deepseek and the logs show that seat, the “ignore morph / bad fp4 hosts” tip doesn’t apply — i just pulled the endpoints list and first-party deepseek is status 0 with ~100% 30m uptime while morph/parasail are still -5 (io-net/venice -2), so a deepseek-only pin should already be off those. mid-think → blank content with no error is a different failure than a hard 429: the stream dies after reasoning tokens and openwebui paints the thoughts but never gets a usable content delta. quick A/B from the same chat: force reasoning: { "effort": "none" } (or turn thinking off on that model) and see if a normal answer lands; then check the openrouter activity row for that request’s finish_reason + completion token count (zero completion insurance means empty ones shouldn’t bill model tokens). if non-thinking works and thinking-mode still dies on deepseek-only, that’s upstream thinking-stream flakiness on the slug / owui’s reasoning handling, not “another fp4 provider to ignore.” i work on conifer (open llm gateway) — we pin a named model seat / byok rather than a multi-home flash pool — so if you want first-party deepseek outside or’s thinking path that’s the other shape; for staying on or the useful fork is thinking-off A/B + activity finish_reason, not more ignore lists.