From f93db822fd15c369f235ac6df9a00bd885c7bcf2 Mon Sep 17 00:00:00 2001
From: Yuneng Jiang <yuneng@berri.ai>
Date: Wed, 8 Apr 2026 17:53:53 -0700
Subject: [PATCH] fix: treat empty router settings inputs as null instead of
 preserving old values

When a user clears a numeric field in the RouterSettingsAccordion, the empty
input should result in null, not fall through to the previous value from state.
---
 .../common_components/RouterSettingsAccordion.tsx      | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/ui/litellm-dashboard/src/components/common_components/RouterSettingsAccordion.tsx b/ui/litellm-dashboard/src/components/common_components/RouterSettingsAccordion.tsx
index ae4b87a3587..18c5d52b4f7 100644
--- a/ui/litellm-dashboard/src/components/common_components/RouterSettingsAccordion.tsx
+++ b/ui/litellm-dashboard/src/components/common_components/RouterSettingsAccordion.tsx
@@ -241,9 +241,13 @@ const RouterSettingsAccordion = forwardRef<RouterSettingsAccordionRef, RouterSet
               key !== "fallbacks"
             ) {
               const inputEl = document.querySelector(`input[name="${key}"]`) as HTMLInputElement | null;
-              if (inputEl && inputEl.value !== undefined && inputEl.value !== "") {
-                const parsed = parseInputValue(key, inputEl.value, value);
-                return [key, parsed];
+              if (inputEl) {
+                if (inputEl.value !== undefined && inputEl.value !== "") {
+                  const parsed = parseInputValue(key, inputEl.value, value);
+                  return [key, parsed];
+                }
+                // Input exists but is empty — user cleared it, set to null
+                return [key, null];
               }
               return [key, value];
             } else if (key === "routing_strategy") {