The "Failed to load devices" error appears when the Automox console cannot complete the API call that loads your device inventory on the Devices page. It is often transient and clears on its own, but when it persists or affects several users, the browser console and network logs are what let Support pinpoint the cause. Work through the steps below in order.
Applies to
- Users who see "Failed to load devices. Please try again." on the Devices page in the Automox console.
Step 1: Check the Automox status page
Confirm there is no active platform incident at status.automox.com. If an incident is in progress, the error is expected until it is resolved, and no local changes are needed.
Step 2: Browser troubleshooting
If the status page is green, the most common causes are browser cache, cookies, or an extension interfering with the console. Try each of the following, rechecking the Devices page after each step:
- Hard refresh the page to bypass the cache: Ctrl + Shift + R on Windows or Linux, or Cmd + Shift + R on macOS.
- Clear your browser cache and cookies, then sign back in and reload the Devices page. See Clearing Your Browser Cache to Optimize Automox Console.
- Open the console in an Incognito or Private window, which loads without extensions and with a clean cache. If it works there, a browser extension is the likely cause.
- Try a different browser (for example Chrome, Edge, or Firefox) to rule out a browser-specific problem.
An intermittent error that clears after a few minutes and returns later usually points to a transient backend condition rather than your browser. If that is the pattern, still capture the diagnostics in Step 3 the next time it happens so Support can review exactly what failed.
Step 3: Capture browser diagnostics for Support
If the error persists after Step 2, capture what the browser sees behind the scenes and open a ticket with Automox Support. Two captures are useful:
- Browser console errors show the specific failure. Open the browser Developer Tools, reproduce the error, and capture the red error entries. See Gathering Web Browser Console Errors.
- A HAR file records the network requests, including the failed device-inventory call and its response code. See Generating a HAR log file on Google Chrome. The steps in Login Error When Navigating to a New Page also walk through producing a HAR file for this kind of error.
Include both captures, the browser and version, whether more than one user is affected, and the approximate times it occurred. Those network errors are what allow Support to identify whether the cause is a specific API call, a permissions issue, or a backend condition.