Optimizing CRM Loading States: Troubleshooting Tips and Custom Code Impact

Created by Stefan Perchinkov, Modified on Wed, 26 Feb at 6:47 AM by Stefan Perchinkov

Significant updates have been introduced to enhance the loading process on our platform. The previous 9-dot loader has been replaced with a sleek, modern spinner design. This updated loader offers clear visual indicators for tasks like app initialization, data retrieval, and account detail loading.

What to Expect During CRM Loading?

1. Initializing the Application:
This state appears when the app is launched or a page is loaded. The spinner signals the beginning of the loading process and remains active until the required data for the app or page is fully loaded.

2. Loading New Data:

After the app initializes, additional data may need to be fetched in response to user actions, live updates, or periodic refreshes. The spinner indicates that this new data is being retrieved.

3. Retrieving Account Information:

For applications with multiple accounts or sub-accounts, this state activates when switching accounts or accessing specific sub-account details.

4. Infinite Loading State:

Occasionally, a page may fail to load within a set timeframe (e.g., 30 seconds), causing the loader to spin endlessly. In such cases, a "Click Here to Refresh" prompt will appear. Clicking it refreshes the page and clears the browser cache, removing the need for manual cache or cookie clearing.

Important Note:

When the refresh option is used during an infinite loading state, error logs are automatically sent to our servers for further analysis, helping us enhance troubleshooting and improve the overall platform experience.

Impact of Custom CSS and JavaScript

Custom code, such as CSS or JavaScript, can sometimes interfere with the loader's appearance or functionality. Below are common issues and recommended actions:

Custom CSS Conflicts:

Custom CSS, which alters a webpage's style, can override or conflict with the loader's default styling. This can result in unexpected visuals or disrupt animations.

Review and adjust your custom CSS to ensure compatibility with the updated loader design. This ensures that custom styles integrate seamlessly without affecting functionality.

Custom JavaScript Conflicts:

Custom JavaScript may interfere with the loader by modifying its logic or event handlers, disrupting its operations or interactions.

Recommendation:
Test and adapt your custom JavaScript to align with the loader's updated features. This ensures the loader works as intended without disruptions.

Testing and debugging custom code thoroughly is key to resolving conflicts, ensuring that both customizations and default features coexist smoothly.

What to Do if the Refresh Button Doesn't Work?

If the refresh button fails or custom code interferes, manual troubleshooting steps may be required:

  1. Open the Inspection Pane:
    • Right-click on the page and select "Inspect."
    • If the pane opens on the left, click the "more" icon (two arrows) to find the "Application" tab.

Clear Site Data:

  • In the "Application" tab, select "Storage" and then click "Clear Site Data."
  • Browser-specific guides: Chrome, Firefox, Safari, and Edge.

Remove Cookies:

  • Click the lock icon in the URL bar, select "Cookies," and choose "Remove."

Once you've cleared site data and removed the cookies, click "Done."

Hard Refresh:

  • On Mac: Hold Command + R.
  • On PC: Hold Ctrl + F5.
  • Follow browser-specific instructions for Chrome, Firefox, Safari, or Edge.

What If the Page Still Doesn't Load?

If a page remains stuck, especially during login verification, you can resolve it by enabling cookies:

  • Look for a paint icon with a red cross in the search bar.
  • Click it, enable "Allow Cookies for this Site," and refresh the page

Slow CRM Data Loading? Here's How to Troubleshoot:

If your dashboard or specific modules are loading slowly, follow these steps:

Step 1: Use an incognito window to log in.

  • If the issue persists, clear the browser cache.

Step 2: Clear the browser cache:

  • Chrome: chrome://settings/siteData
  • Edge: edge://settings/clearBrowserData?search=cache
  • For other browsers, search for instructions on clearing cookies and cache.

Step 3: Disable browser extensions.

  • Check if the issue persists after disabling all extensions.

Step 4: Try a different browser.

  • Switch to Firefox, Safari, or Chrome and test again.

FAQ: Enhanced CRM Loading States

1. What are the new improvements to CRM loading functionality?

The platform now uses a modern spinner design instead of the previous 9-dot loader. This updated design provides visual feedback for app initialization, data fetching, and account detail retrieval, offering a clearer user experience.

2. What does the infinite loading state mean, and how can I resolve it?

An infinite loading state occurs when a page fails to load within a set timeframe. Use the "Click Here to Refresh" prompt to reload the page and clear the cache automatically. If the issue persists, try clearing your cookies and site data manually.

3. How can custom CSS interfere with the loader?

Custom CSS may override or conflict with the loader’s default styling, affecting its animations or appearance. Review and adjust custom styles to ensure they work seamlessly with the updated loader design.

4. Can custom JavaScript impact the loader's performance?

Yes, custom JavaScript may disrupt the loader’s event handlers or logic, leading to functionality issues. Ensure your custom JS is tested and updated to align with the loader’s new features.

5. What should I do if my CRM data loads slowly?

Log in using an incognito window to check if the browser cache is the issue. Clear your browser’s cache and cookies. Disable browser extensions and test again. If the issue persists, try using a different browser like Firefox, Safari, or Chrome.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article