Hello Team,
We are currently encountering the following error in our web application:
"Failed to execute 'setItem' on 'Storage': Setting the value ${OS_AppName}$FallbackLocalStorage exceeds the quota."
As a result, users are unable to log in.
I have already reviewed the related post regarding this issue. However, I would like to explore if there are any alternative solutions, as we do not want to require end users to clear their local storage each time this issue occurs.
I appreciate any insights or recommendations you can provide.
Thanks in advance!
If the data doesn't need to persist across browser sessions, use sessionStorage instead of localStorage. It has a similar API, but its data is automatically cleared when the page session ends.
Please check if you can minimize what's stored in Local Storage.
Also, instead of asking users to clear full storage, you can add code to remove your app's key when it goes over limit. JS can be used here which will clear Outsystem's fallback cache, it will not clear user data.
The error occurs because you’re storing data in localStorage that exceeds its size limit.
This limit varies by browser (typically around 5–10 MB total for all key–value pairs per domain).
To fix this issue, optimize or reduce the amount of data you’re saving in localStorage.
Hi Lavanya,
As mention by the folks, this usually happens when the local storage size limit (around 5–10 MB depending on the browser) is exceeded. Apart from clearing or reducing the data stored, try reviewing what’s being cached — especially large JSON objects or logs. If your app relies on OutSystems fallback storage, you can also move non-critical data to session or server variables to avoid hitting the browser quota again.
Hope this helps you stabilize the login flow!Thanks and Regards,Akshay Deshpande