Issue Station
Sign In
Tools hereToolbox

litellm - 💡(How to fix) Fix [Bug]: UI healtcheck not reflecting the reality. [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#24862•Fetched 2026-04-08 01:59:05
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
EludendilEludendil
Participants
EludendilEludendil
Timeline (top)
labeled ×1

Code Example

litellm=# SELECT status, checked_at FROM "LiteLLM_HealthCheckTable" ORDER BY checked_at DESC LIMIT 2;
  status   |       checked_at
-----------+-------------------------
 healthy | 2026-03-31 14:47:50.859
 healthy   | 2026-03-31 14:47:50.345
(2 rows)

---

litellm=# SELECT status, checked_at FROM "LiteLLM_HealthCheckTable" ORDER BY checked_at DESC LIMIT 2;
  status   |       checked_at
-----------+-------------------------
 unhealthy | 2026-03-31 14:48:50.859
 healthy   | 2026-03-31 14:47:50.345
(2 rows)

---
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

So i have Two model plug. And reporty heallthy on the UI.

I check the psql state:

litellm=# SELECT status, checked_at FROM "LiteLLM_HealthCheckTable" ORDER BY checked_at DESC LIMIT 2;
  status   |       checked_at
-----------+-------------------------
 healthy | 2026-03-31 14:47:50.859
 healthy   | 2026-03-31 14:47:50.345
(2 rows)

I intentionally break one of them and recheck the psql table.

litellm=# SELECT status, checked_at FROM "LiteLLM_HealthCheckTable" ORDER BY checked_at DESC LIMIT 2;
  status   |       checked_at
-----------+-------------------------
 unhealthy | 2026-03-31 14:48:50.859
 healthy   | 2026-03-31 14:47:50.345
(2 rows)

So far so good. However on the UI it is stuck on the Healthy status and will never progress to the unhealthy one. If i manually trigger the healthcheck button it does return unhealthy but if I refresh the page it goes back to the healthy state....

Steps to Reproduce

Relevant log output

What part of LiteLLM is this about?

No response

What LiteLLM version are you on ?

v.18.3

Twitter / LinkedIn details

No response

extent analysis

TL;DR

The UI may not be updating in real-time to reflect the unhealthy status of one of the models, suggesting a potential issue with the health check update mechanism.

Guidance

  • Verify that the UI is properly configured to poll the LiteLLM_HealthCheckTable for updates, and that the polling interval is set to a reasonable value.
  • Check the UI code to ensure that it is correctly handling the case where one of the models is unhealthy, and that it is not caching or overriding the unhealthy status.
  • Investigate the possibility of a race condition or timing issue that could be causing the UI to revert to the healthy status after a refresh.
  • Review the health check button's implementation to understand why manually triggering it returns the correct unhealthy status, but the UI does not update automatically.

Example

No code snippet is provided as the issue does not contain sufficient information about the UI implementation.

Notes

The issue may be related to the UI's update mechanism or the health check implementation, but more information is needed to provide a definitive solution.

Recommendation

Apply a workaround, such as increasing the polling interval or implementing a more robust update mechanism, to ensure the UI accurately reflects the health status of the models.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#vector store#embedding generation#cache error#pipeline error#runtime error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING