mirror of
https://github.com/BaaRai/ARTEX.git
synced 2026-11-19 06:30:54 +08:00
The /system/llm/ badge read llm_profile_health, which only the failover Pool wrote. A task pinned to an explicit chain, a bound agent with failover off, and the global provider all call the provider directly, so a dead backend stayed "Healthy". One policy now lives in llmpool.Registry.RecordCall, used by the Pool and by the task runtimes: a success clears the state, a failover-eligible failure trips it, context cancellation and deterministic 400s do not, and a stream that already delivered output is left alone. The selection carries the profile whose breaker the call updates, and a provider already wrapped in the Pool reports nothing to avoid double counting. The LLM recording page also explains an empty list while the llm_record toggle is off, after the settings call resolves. Originally reported in #257.