The HubSpot Sales extension is forcing my Gmail into an endless reload loop every 30-60 seconds. The sprocket icon is grey and the sidebar will not load. Clicking restart extension in the HubSpot sprocket does nothing
I have tested this on a brand-new, completely clean Chrome profile with zero other extensions installed, and the exact same crash and reload loop occurs. This is not a local cache issue; this is a reproducible bug in the current extension build colliding with Gmail.
I did this because my own Chrome profile which previously worked perfectly for years was reloading every 30-60 seconds. To troubleshoot, I updated Chrome. I deleted and reloaded the HS extension. I logged out of hubspot.com and then back in. I toggled my Gmail settings on/off from the Email tab in Settings at hubspot.com. I have deleted as many cache files as I can from within Chrome and in macOS Finder. I have run Disk Utility after a macOS restart. I ran a cache cleaner for macOS. When I did this yesterday something worked and I was able to use the extension in Gmail.
Today, the problem is back and nothing fixes it. I did so many things yesterday that it’s possible I am forgetting something but it shouldn’t be this hard. Everything I tried today made no difference other than the HS sprocket won’t even show up in Gmail at all, even with a newly installed version of the HS extension enabled.
After creating a brand new Chrome profile and seeing the same thing happen shows me there’s really something odd happening.
If I disable the HS extension everything works fine but I need this extension to work.
Sorry if this is sloppy. I have literally typed this our so many times into Gemini and Google and HS chat to try to get support I am freaking loopy AF.
Hi @luckylou and welcome, it’s a pleasure to have you here!
Thanks for reaching out to the HubSpot Community!
It’s great to see that you’ve tried all the usual and recommended troubleshooting steps! Sharing this resource in case another Community Member has the same behavior: “Troubleshoot the HubSpot Sales Chrome extension”
Also, I’ve been reading through your discussion with HubBot and thanks for checking existing Community threads also.
Since you’ve ruled out most local factors, I’ll investigate this internally for you but I’ll need some additional information so I’ll reach out via DM for this.
In the meantime, if you notice any patterns, like specific actions that trigger the reload loop, please share them here.
I’d love to hear from our Top Experts: Hi @danmoyle, @trevordjones and @Mike_Eastwood do you have any insights to share with @luckylou, please?
And if anyone else in the Community has experienced and resolved a similar issue, let’s connect here!
Thanks so much and have a lovely day!
Bérangère
Welcome to the Community @luckylou. Sorry this has made you so loopy. I agree, it shouldn’t be this difficult to use the tools. Are you on a tier with access to HubSpot Support? I’d definitely escalate this to them if you can. It sounds like you’ve run through troubleshooting I’d suggest, and what I’d have looked up in Breeze Assistant and other AI tools.
HubSpot’s documented escalation path is to send extension debug logs from Gmail sprocket → Help & troubleshooting → Need more help? → Send debug logs. Since your Gmail sprocket is not usable, tell Support that explicitly and attach the information above instead.
If that’s not possible, the only other thing I found in addition to what you’ve been trying is this from HubSpot’s Knowledge Base: Also ensure third-party cookie permissions explicitly allow [.]getsidekick.com, [.]hubspot.com, and [*.]hsappstatic.net; HubSpot identifies those domains as required when third-party-cookie blocking is enabled. This is more relevant to a grey/inert sprocket and missing sidebar than to a full Gmail reload loop, but it is worth validating once.
I haven’t personally had any issues lately with the extension, so I don’t have a personal fix. Hopefully this helps some anyway?
Moderator note: While this solution may not address the original poster’s specific situation, it could be helpful for other community members facing similar challenges.
I’m not sure why someone marked this as Solved when the suggestion was to escalate to support. I don’t block third party cookies but I did see the suggestion in the KB to specifically allow [.]getsidekick.com, [.]hubspot.com, and [*.]hsappstatic.net, which I already did. I tried everything.
But I actually did solve the problem. My computer had already been running slow with a high fan regardless of cahce resets and restarts. I realized I had a ton of tabs open, so I closed a ton of tabs. The machine started running better. I decided to reinstall the HS extension and toggle Gmail on/off in HS settings at .com.
Gmail reloaded. Nothing. Then the sprocket appeared after along time. This time it had a red light, not grey, and it allowed me to click on it and manually activate it. The sidebar icon appeared and it works fine now.
So - if HS extension is failing, it could be too many tabs open!
Hi @luckylou, thank you for your feedback and for sharing the steps you took to resolve the HubSpot extension behavior you were seeing! So glad to hear that all is working for you now!
It’s a great reminder that something as simple as having too many browser tabs open can impact extension performance.
I’ve marked Dan’s reply as a solution so other Community members can easily find these helpful suggestions, thanks for your understanding.
Community Champions, like @danmoyle, are not HubSpot employees, but enthusiastic volunteers committed to helping and supporting everyone in the Community, and we love thanking them for their selfless contributions & knowledge-sharing by accepting their helpful replies as solutions.
If you have additional questions, please feel free to update this topic or start a new one, we’re always here to help!
Thanks again and have a lovely weekend!
Bérangère
- Please note that I’m out of the office until August 27th -
Hey, I appreciate Dan generously stepping in to assist and making his considerable services available.
That said, his post wasn’t the solution.