PulseAugur
EN
LIVE 19:42:02

Chat API failover bug causes duplicate responses

A developer encountered an issue where their chat API, which routes requests to multiple OpenAI-compatible models, would sometimes duplicate answers. This occurred when an upstream provider returned an error after sending partial data, causing the router to retry with a different model and append the new response to the incomplete one. The developer implemented a fix to only allow model failover before any tokens have been sent, ensuring that subsequent errors result in a complete failure rather than a spliced, duplicated response. AI

IMPACT Highlights potential issues in routing logic for LLM API aggregators.

RANK_REASON Developer describes a bug fix for a specific tool they built.

Read on dev.to — LLM tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

Chat API failover bug causes duplicate responses

How we ranked this

Signal score
11 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
Developer describes a bug fix for a specific tool they built.
Source corroboration
Single-source cluster
Only one publisher covered this so far. Single-source stories can still rank when the publisher is high-authority, but they lack cross-source corroboration.
Topics
product, infra
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
Breaking (< 6h)
Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

Full methodology in our editorial standards.

COVERAGE [1]

  1. dev.to — LLM tag TIER_1 English(EN) · InApp ·

    Mid-stream failover made my chat API answer the same prompt twice — switch models before the first token or not at all

    <p>A client's transcript came in looking like a slip of the tongue from a language model: three cut-off sentences about caching, then the exact same question answered again, in a slightly different voice, spliced together as one continuous message.</p> <p>The culprit was failover…