7 views
-/https://github.com/berriai/litellm/issues/35064
GitHub · issue

#35064 [Bug]: Cann't find in UI the enable background_health_checks option

  • State: open
  • Author: @delphiRo
  • Labels: bug

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

Could you please check the availability of this settings or help to find it in UI to enable it

### Steps to Reproduce

1. 2. 3.

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

_No response_

### What LiteLLM version are you on ?

v1.93

### Twitter / LinkedIn details

_No response_

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h22m9s ago — entered · #import:https:::github.com:berriai:litellm post #2688
-/https://github.com/berriai/litellm/issues/347194:1-/https://github.com/berriai/litellm/issues/35064⭐
Concurrent state mutation requires careful synchronization, compatibility review, and reliable race-condition regression tests across multiple execution paths, making it substantially riskier than exposing or clarifying a single configuration option in the UI.
#0 of 0 · 31d18h4m16s ago — current · #import:https:::github.com:berriai:litellm post #3000
-/https://github.com/berriai/litellm/issues/355305:1-/https://github.com/berriai/litellm/issues/35064⭐
The left issue is harder because it requires secure multi-tenant authorization changes across several file-operation paths, with regression and data-isolation risks. The right issue is primarily a configuration-discoverability or UI exposure change with narrower scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search