The “Failed to Fetch” error usually appears when BuildOps can’t fully load due to browser data, network restrictions, or security settings. In most cases, it can be resolved quickly by following the steps below.
We recommend trying these steps in order, starting with the quickest fixes.
Step 1: Quick Browser Checks
Use a supported browser
Make sure you’re using Google Chrome (desktop).
Update Chrome to the latest version.
If you’re using Edge, Safari, or another browser, switch to Chrome and try again.
Many customers see this error disappear simply by switching to Chrome.
Refresh and re-login
Refresh the page using Ctrl + Shift + R (Windows) or Cmd + Shift + R (Mac).
Log out of BuildOps.
Close all browser tabs.
Open a new tab and log back in.
Try an Incognito window
Open a Chrome Incognito window.
Log in to BuildOps.
If BuildOps works in Incognito but not in a regular window:
Clear cache and cookies for
live.buildops.comandlive.buildops.org.Temporarily disable browser extensions (especially ad blockers, VPNs, or security plugins).
Step 2: Check Your Device and Network
If the issue continues, it may be related to your device or network.
Try another device
Log in using a different computer on the same network.
If available, test from a personal laptop or home device.
If it only fails on one device, this usually points to local browser or security settings.
Test a different network
Switch to another network (for example, a mobile hotspot).
If it works on a different network, your office network may be blocking some requests.
Step 3: Review Security and Network Settings
If you’re on a managed or corporate network, check with your IT team to confirm:
There are no firewall or security rules blocking BuildOps traffic.
Browser privacy or security settings aren’t interfering with requests.
VPNs or network monitoring tools are not blocking access.
Still Having Trouble?
Before reaching out:
Make sure the browser tab is fully closed and reopened.
Confirm you’ve tried the steps above.
If the “Failed to Fetch” error still appears after troubleshooting, our Support team is happy to help. Let us know:
The browser and version you’re using
Whether the issue happens in Incognito
Whether it works on another device or network