[GH-ISSUE #16631] issue: Saving config saves all settings even though not all of them have been updated #56651

New Issue

GiteaMirror · 2026-05-05T19:53:08-05:00

GiteaMirror commented

2026-05-05 19:53:08 -05:00

Originally created by @Rain6435 on GitHub (Aug 14, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16631

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

v0.6.22

Ollama Version (if applicable)

0.9.6

Operating System

Ubunutu 22.04

Browser (if applicable)

No response

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Logically, if I only change a value of the config using whatever method, mainly through the admin panel, it would be great that the saving only targets what I changed.

Actual Behavior

Currently, the whole config is saved even after changing one single element. Also, the saving is sequential, so if my changed value is only saved at the end of the sequential process , I still get the toast that the saving has been successful although the actual saving of my changed value might not have been done yet.

Steps to Reproduce

Have the backend and frontend running.
For my instance, I updated a Banner.

Create a Banner, save it and try reloading right after. Your save will not take place until saving the WEBUI_BANNERS is completed, and this is the last step of saving the config.

To view that, after clicking on Save, look at the logs of the backend.

Logs & Screenshots

No logs really for this except for what the backend says.
This is more of a performance bug.

Additional Information

A solution to that would be to would be to compare the config before saving.
The differences would be the one subject to saving.

backend/open_webui/config.py handles the saving of configs.

Originally created by @Rain6435 on GitHub (Aug 14, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16631 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version v0.6.22 ### Ollama Version (if applicable) 0.9.6 ### Operating System Ubunutu 22.04 ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Logically, if I only change a value of the config using whatever method, mainly through the admin panel, it would be great that the saving only targets what I changed. ### Actual Behavior Currently, the whole config is saved even after changing one single element. Also, the saving is sequential, so if my changed value is only saved at the end of the sequential process , I still get the toast that the saving has been successful although the actual saving of my changed value might not have been done yet. ### Steps to Reproduce Have the backend and frontend running. For my instance, I updated a Banner. Create a Banner, save it and try reloading right after. Your save will not take place until saving the WEBUI_BANNERS is completed, and this is the last step of saving the config. To view that, after clicking on Save, look at the logs of the backend. ### Logs & Screenshots No logs really for this except for what the backend says. This is more of a performance bug. ### Additional Information A solution to that would be to would be to compare the config before saving. The differences would be the one subject to saving. backend/open_webui/config.py handles the saving of configs.

GiteaMirror added the bug label 2026-05-05 19:53:08 -05:00

GiteaMirror closed this issue

2026-05-05 19:53:09 -05:00

GiteaMirror commented

2026-05-05 19:53:10 -05:00

@tjbck commented on GitHub (Aug 14, 2025):

Intended behaviour.

@tjbck commented on GitHub (Aug 14, 2025): Intended behaviour.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#56651