Troubleshooting the Web App

The web app at app.wallfacer.ai keeps a small amount of data in your browser's storage so a reload starts fast. Browsers cap that storage per site, and the issues below all come from hitting the cap.

Signed Out After a Reload

Symptom: You reload the app and land on the sign-in screen, even though you signed in a moment ago and never signed out.

Cause: Your browser's storage for the site is full, so the app couldn't save your sign-in. The app works normally for the rest of the visit because it holds the sign-in in memory, but there is nothing to restore on the next load.

Fix: Clear site data for app.wallfacer.ai in your browser's site settings, then sign in again. Clearing the site data frees the whole quota, including the app's cache, so the next sign-in has room to persist.

Data Looks Out of Date Right After a Reload

Symptom: Just after a reload, something like your accounts list shows an older state for a moment before catching up.

Cause: The same full storage. A cache write that can't land leaves the previous value in place, so the reload renders from a stale copy.

Fix: Nothing is required. The app refetches from the server on load and corrects itself within a second. To stop it recurring, clear site data for app.wallfacer.ai.

What the App Stores in Your Browser

The app caches your sign-in, your accounts list, and recently viewed data. The cache is capped well under the browser's limit for the site, and the app drops the least recently used entries first to stay under the cap, so the app's own cache does not fill your quota. Other pages on the same origin can still fill it.

Two things are deliberately not cached:

• Session messages. Reopening a session loads its history from the server, so you may see a brief load before the conversation appears. The server copy is the current one, which a cached copy can't guarantee after a tab has been closed for a while.
• VM and snapshot logs. Logs are unbounded and live-tailed, so they load fresh each time you open them.

When the browser refuses a write, the app keeps running from memory rather than failing to load. Your work is stored on the server, so a full browser storage costs you a sign-in and a fast start, never a session or a task.