Follow these four steps to troubleshoot "spinning wheel" screens at workflows.anvl.com.
Step 1: Restart Your Session (Log Out and Log Back In)
A simple restart is often enough to resolve minor session conflicts.
Log out of the application completely.
Close your browser window.
Re-open your browser and navigate back to the app.
Log in again.
If the problem persists, move to Step 2.
Step 2: Clear Your Browser's Cache and Cookies
Your browser often saves older versions of our app's files (called "cache") to speed things up. Sometimes, these old files conflict with new updates.
Click the three dots (Menu) in the top-right corner of your browser.
Go to More Tools > Clear browsing data.
In the pop-up window:
Set the Time range to "All time".
Check only the boxes for "Cookies and other site data" and "Cached images and files".
Click the "Clear data" button.
Once done, return to the application and test if the issue is resolved.
Step 3: Try an Incognito or Private Window
To rule out any browser extensions or specific settings on your profile, try running the app in a clean environment.
Click the three dots (Menu) in the top-right corner.
Select New Incognito Window (or "New Private Window" in other browsers).
In the new window, navigate to our app and log in.
See if the error occurs in this window.
If the app works in Incognito mode, the problem is likely an old session, a conflicting browser extension, or a setting on your main profile.
Step 4: Send a Screenshot from Developer Tools (For Support)
If the problem still isn't fixed, the technical details in your browser's console will help us diagnose the issue.
Open our app in your browser and try to trigger the error.
Open the Developer Tools by pressing F12 (or
Ctrl+Shift+I/Cmd+Option+I). This will open a panel on the side or bottom of your screen.Click the Console tab in the Developer Tools panel.
Take a screenshot of this tab, making sure to capture any red error messages.
Also, check the Network Tab:
Click the Network tab in the Developer Tools panel.
Refresh the page (or re-trigger the error).
Look for any red-colored entries that have a "401" or "500" status code.
Take a second screenshot of this list.
Send both screenshots to our support team. The error messages in the Console and Network tabs are the technical clues we need to fix the issue on our end!