What this guide covers
Why browsers store cache and how it affects BrightMove
The difference between cache and cookies (and why that matters)
BrightMove’s new Local History shortcut (clear BrightMove-only saved views in one click)
Step‑by‑step fixes: hard refresh, BrightMove‑only reset, site‑specific cache clear, and full browser instructions
What you’ll (and won’t) lose when you clear things
Quick fix (most users)
Hard Refresh the page (least invasive):
Windows/Linux:
Ctrl + Shift + RMac:
Cmd + Shift + R
Use BrightMove’s Local History link (clears BrightMove-only saved views):
Go to My Quick Links → Settings → Local History.
Click Local History once. The page will refresh with a clean, up‑to‑date view.
Return to the page you were using and try your action again.
Example: After a new release, let's say you don’t see the Submittal Status column on a Job. Try a hard refresh first. If it’s still missing, go to My Quick Links → Settings → Local History, then return to the job list, the view will load correctly going forward.
Why cache exists (plain English)
Every web browser stores a cache of the websites you visit, things like BrightMove pages, HTML files, and images. This speeds up page loads, reduces bandwidth usage, and lowers server load. Over time, however, cached files or saved page settings can fall out of sync with the newest BrightMove version. That’s when you can see stale columns, stuck filters, or pages that won’t render.
Clearing your cache lets BrightMove load fresh code and assets, enabling new features that weren’t appearing before. It can also free up space on your computer’s hard drive if you’re running low.
Note: Deleting your browser’s cache is not the same as deleting cookies. Cache stores files to speed up pages; cookies store things like login sessions and site preferences.
When should I clear cache or Local History?
A BrightMove page is acting oddly right after a product update
A grid won’t load, shows old columns/sorting, or filters won’t “stick”
Buttons don’t respond, or the page spins indefinitely
BrightMove works in Incognito/Private mode but not in your normal window
Start with a hard refresh, then do Local History (BrightMove‑only).
What the Local History link does
Clears BrightMove‑specific saved views and settings (e.g., grids, filters, column selections)
Does not touch your browser-wide cache, bookmarks, passwords, or other sites
Safest, fastest first step to get a fresh, compatible view after updates
How to use it
Go to My Quick Links → Settings → Local History
Click once, wait for the page to refresh
Navigate back to your work. Columns and views should now render correctly
Step‑by‑step fixes (in order)
1) Hard refresh (cache‑bypass)
Windows/Linux:
Ctrl + Shift + RMac:
Cmd + Shift + R
2) Try a Private/Incognito window
If BrightMove works there, stale local data is likely in your normal window. Use Local History or clear site data for BrightMove only.
FAQs
Is clearing Local History the same as clearing cache?
No. Local History clears BrightMove‑specific saved views/settings. Clearing cache removes downloaded files the browser uses to speed up pages.
Will I be signed out?
Using Local History usually will not sign you out. Clearing site data typically will, be ready to sign back in.
Do I need to clear my entire browser cache?
No. Start with Local History, then (if needed) clear site data for BrightMove only.
Why do issues appear after a release?
Saved views can become incompatible with the newest BrightMove code. A quick Local History clear or cache refresh realigns your browser with the latest version and features.
Still need help? Send this to Support
What I tried: Local History / hard refresh / site‑specific clear
Exact page & action: (e.g., Jobs → Open Jobs → sorted by Created Date, then Export)
When it started: (date/time; mention if a release just happened)
Browser & version: (e.g., Chrome 128 on Windows 11)
Console errors (if any): first 1–2 lines
Optional: localStorage key list (before clearing)
Good to know: Clearing cache periodically can also free disk space and ensure BrightMove is using the latest features and assets.