Clearing cache/cookies is often the fastest fix in NEXA ERP when you can’t log in or tables don’t load, because browsers can get “out of sync” with the server after updates or session issues.
Why it helps (what usually goes wrong)
1) Broken/expired session or auth cookie
- Login relies on cookies (session/JWT, CSRF token, “remember me”).
- If that cookie is expired, corrupted, or from an older version, the server rejects requests → you see login loops, “unauthorized”, or you can’t stay logged in.
- Clearing cookies forces a fresh session and new tokens.
2) Old cached JS/CSS after a system update
- If NEXA ERP was updated, the browser may still use old JavaScript from cache.
- Old JS calls the API differently or expects different response fields → UI breaks, buttons stop working, tables never populate.
- Clearing cache forces the browser to download the latest frontend files.
3) Cached API responses / service worker (PWA) conflicts
- Some setups cache API responses or use a service worker.
- If the cached layer is stale, the app can show blank tables or fail silently.
- Clearing site data removes those stale stored files.
4) Local storage/session storage conflicts
- Many ERPs store UI state, user role, last branch, filters, token, etc. in LocalStorage.
- If those values become inconsistent (e.g., user role changed, branch removed), it can break loading of screens/tables.
- Clearing site data resets that state.