You selected Save Changes (or similar) on a settings screen and nothing happened — no success message appeared, or the page looks the same when you come back. There are a few common causes.
What's happening
Cause 1 — A validation error is blocking the save silently. Some field values are validated before the save is sent. If a colour hex value is malformed, a name is too long, or a required field is blank, the save may be prevented without a visible error in some browser configurations.
Cause 2 — The save succeeded but the browser is showing a cached version. After saving branding settings, the admin portal theme applies the new values immediately to the live document. If a page refresh shows the old values, the browser may be serving a cached copy.
Cause 3 — A network or server error occurred. An error toast should appear, but if your connection dropped at the exact moment of saving, the toast may not have rendered.
How to fix it
-
Check for field-level errors. Scroll through the form and look for red highlighted fields or advisory text. On the branding page, each colour field shows a contrast advisory — an invalid hex (not matching the pattern
#RRGGBB) will block saving. Correct any invalid values and try again. -
Reload the page and check the saved values. After a successful save, the form re-fetches the authoritative values from the server. If you reload and see your changes, the save worked and the issue was display-only.
-
Re-enter and save again if values reverted. If a reload shows the old values, the save did not complete. Re-enter your changes, wait for a clear Branding saved or similar success message (a green toast at the top of the screen), then reload to verify.
-
Check your connection. If you have an unstable internet connection, saves can fail mid-request. Confirm you are connected, then try saving again.
-
Hard-refresh the page. Use Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac) to bypass the browser cache and reload from the server.
Notes
- On the branding page, clicking a Dashboard Theme palette applies it with its own request — if that request fails, an error toast will appear. Palette changes and manual colour saves are separate operations; confirm each shows a success message.
- If Save Changes is greyed out, no fields have been changed from the current saved state. Make a change first.
- For persistent save failures, contact support.