My clients are getting this when using some of my Pickaxes. I’ve had two disruptive days here guys with my clients running into errors and bugs. Please advise how to fix this? I looked at the other threads with this as it seems like a common issue but it doesn’t really tell me anything.
Totally hear you. This error looks scary, but in many cases it’s not actually a Pickaxe bug. It’s usually the browser getting in the way.
Here’s what’s most likely happening, in plain terms:
Something in the browser is interfering while the Pickaxe page is loading. We’ve seen this happen when browser extensions inject extra code into the page. Common culprits are page translators, VPNs, ad blockers, privacy tools, or anything that modifies websites as they load. When that happens, the page can crash before it finishes loading, which triggers this “client-side exception” message.
A few simple checks usually help narrow this down quickly:
• Turn off browser extensions temporarily, especially translators and VPNs, then reload the Pickaxe
• Open the same Pickaxe in an incognito or private window. This skips extensions and cached data in most cases
• Clear browser cache and cookies, then try again
• Try a different browser or device to see if it works there
If the error still shows up, the next helpful step is the browser console. This is where the browser logs exactly what went wrong.
You can open it by pressing F12 or right-clicking on the page and choosing Inspect, then clicking the Console tab. A quick screenshot of any red error messages there will give our engineering team very clear signals about what’s breaking.
I know this has already cost you time with clients, and I’m really sorry about that. If you want, you can also send the details and screenshots directly to info@pickaxe.co and we’ll take it from there. We’ll help you get this sorted.
1 Like