Troubleshooting the Web App
Published
Updated
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 browser settings that block site storage can stop Google sign-in. A rejected sign-in can also return you to the login screen.
The Login Screen Says Your Session Has Ended
Symptom: While using the web app, you return to the login screen with the message "Your session has ended. Log in again to continue."
Cause: Wallfacer rejected the current sign-in. The app ends that session so you can sign in again instead of leaving you on a screen that cannot load data.
Fix: Log in again. The message clears after you sign in. You do not need to clear browser storage for this message.
The App Says This Account Is Suspended
Symptom: Instead of your tasks and agents, the web app shows "This account is suspended" with Contact support.
Cause: The Wallfacer team has suspended the account. Nobody can use it until it is resumed.
Fix: Select Contact support to email us; we will tell you why the account was suspended and what resumes it. When it is resumed, the app returns to the product on its own, without a reload. If you belong to other accounts, pick one under Use another account, or select Sign out.
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 cache write, the app keeps running from memory rather than failing to load. Your work is stored on the server, so full browser storage can cost you a saved sign-in and a fast start, never a session or a task.
Google sign-in needs site storage to keep the sign-in request in the same browser tab while you visit Google. If that storage is blocked or full, Continue with Google stops before opening Google's page and shows a message. Allow site data for app.wallfacer.ai and try again, or use your email and password. See Signing In.