Sparkforge Loading States and Custom CSS/JS Conflicts

By Sparkforge Support Team ·Last reviewed May 3, 2026

Sparkforge shows four loading states (initialize, fresh data, sub-account, infinite). If a page hangs, custom CSS or JS is usually the cause — clear site data, remove cookies, and hard-refresh. Persistent issues often mean the user isn't assigned to a sub-account.

Sparkforge replaced the old 9-dot loader with a spinner that signals which loading phase is running. This article covers each state, how custom CSS or JS can interfere, and the manual recovery steps when the page hangs.

The four loading states

Initializing the App

The first state. The spinner runs while the app or page boots and stays active until the required data is fetched.

Loading Fresh Data

Triggered after initial load when new data is being pulled — user actions, real-time updates, or scheduled refreshes.

Retrieving Sub-account Details

Activated when switching between sub-accounts or loading sub-account-specific data.

Infinite Loading State

The page hasn't loaded within the predefined timeout (around 30 seconds). A Click Here to refresh prompt appears. Clicking it reloads the page and clears the browser cache automatically — no need to manually clear site data.

When you trigger the refresh action, error details get forwarded to Sparkforge engineering for analysis.

Custom CSS and JS interference

Custom CSS

If your custom CSS overrides loader classes or animations, the visual state can break — the loader may not render correctly or fail to clear when data loads. Audit any custom CSS that touches loader, spinner, or overlay classes.

Custom JS

Custom JavaScript that overrides event handlers or modifies the loader's DOM can prevent it from clearing or block user interactions. Test custom scripts in isolation before deploying them across sub-accounts.

Manual recovery: page is stuck

If the refresh button doesn't fire, do this manually.

Right-click the page and choose Inspect.
If the panel docks on the left, open the "more" menu and find the Application tab.
Inside Application, open Storage and click Clear Site Data.
Click the lock icon next to the URL, choose Cookies, and remove the site cookies.
Hard refresh the page. Mac: Cmd+R. Windows: Ctrl+F5.

Confirm user access to the sub-account

If a user keeps hitting loading errors, check that they're actually assigned to the sub-account.

Open Agency View > Team Management.
Search by name, email, or phone.
Click Edit > User Roles.
Confirm at least one sub-account is selected in the dropdown.

If you aren't the agency owner, contact the agency admin to restore your sub-account access.

Frequently Asked Questions

Why does the Sparkforge page keep loading without finishing?

Most often a custom CSS or JS conflict is blocking the loader from clearing. Click the Click Here to refresh prompt, or manually clear site data and hard-refresh.

What does the refresh button actually do?

It reloads the page, clears the browser cache automatically, and forwards error details to Sparkforge engineering so the issue can be diagnosed.

I cleared site data and the page still hangs. What now?

Confirm your user is assigned to the sub-account in Agency View > Team Management > User Roles. If you aren't the agency owner, ask them to add you back.

Will my custom CSS or JS break the new loader?

It can. Any custom code that overrides loader classes, animations, or event handlers may prevent the spinner from clearing. Audit and test custom code before rolling it out.