Skip to main content
Browser extension

Troubleshooting the extension

Find out what the QuantumOps extension is doing from Options and its Diagnostics section, and fix the problems people meet most often.

Written By Chris Scaminaci

Last updated About 1 hour ago

When the QuantumOps side panel does not do what you expect, start with the extension's Options page. Its Diagnostics section shows what the extension knows about itself and what the browser has allowed it to do, and it is what your administrator asks for first. This page explains that section, lists the fixes for the problems people meet most often, and says what to send when you need help.

Before you start: open Options in any of three ways: select the gear in the panel's status bar, select Open options on the welcome page, or right-click the toolbar icon and choose the extension's options entry (Options in Chrome, Extension options in Edge). In Firefox, open the add-ons page (about:addons), select QuantumOps for Halo and open its options.

Read the Diagnostics section

The Diagnostics section of Options says Send this section to your administrator when something does not work. It lists:

FieldWhat it tells you
Extension versionThe version that is running.
Extension idThe identity the browser gave the extension.
Install typeHow the extension was installed, in the browser's own words: normal for a store install, admin for an install by your administrator's policy, development for a bundle loaded from a folder or a temporary add-on, and sideload for an install by other software.
OAuth redirect URIThe return address your sign-in service must know for this browser. An administrator may ask you for it.
Realtime hubThe state of the live-updates connection the last time the panel was open: connected, connecting, reconnecting or disconnected. It shows panel not open if the panel has not been opened since the browser started. Open the panel before you read it.
Remote config fetchedWhen the extension last downloaded its settings from your instance, or never.
Minimum version requiredThe oldest extension version your instance still supports. A version below it gets an Update required notice.
Update checkThe result of the last check for a newer version, in one sentence.
Granted originsThe sites the browser lets the extension reach: your QuantumOps address and the HaloPSA domains.
PermissionsThe browser permissions the extension holds.

Re-check permissions makes the extension check every site the browser has granted and register the HaloPSA page-following for each one again. Use it after your administrator changes a browser policy, or after you revoke and grant a site in the browser's own settings. The extension runs the same check when the browser starts and whenever you add or remove a domain.

If your administrator blocks the HaloPSA address, or the scripting permission, with a browser policy, the panel cannot follow HaloPSA pages. Granted origins shows whether the browser gave the extension a site, and Permissions shows the permissions it holds. A site can be listed and still be blocked by your administrator's policy, so if the panel does not follow a listed domain, ask your administrator.

Fix a problem

What you seeWhy it happensWhat to do
The sign-in button reads Set the QuantumOps URLThe extension has no address for your instance, or has not loaded its sign-in settings yet.In Options, enter the address under QuantumOps instance and select Use this URL. If the button does not change, sign-in may not be set up for your instance; tell your administrator.
Options says Enter a valid https URL for your QuantumOps instance. or Permission for the API origin was not granted; the panel cannot call it.The address is incomplete, or you declined the browser's permission prompt.Enter the full address, starting with https://, select Use this URL and allow the permission.
Options says Could not load configuration from followed by your address and a reason.The address is valid, but it is not your QuantumOps instance, or the instance cannot be reached.Copy the address again from the Browser Extension page, select Use this URL, and tell your administrator if the message comes back.
The sign-in window fails at once. Chrome and Edge say Authorization page could not be loaded, or Last error in Options names a redirect address.Your sign-in service does not know the return address of this browser.Send the OAuth redirect URI from Diagnostics to your administrator. Nothing on your side fixes it.
Sign in cannot start, and Options shows no sign-in settings.Sign-in has not been set up for your instance.Tell your administrator. The Browser Extension page shows whether sign-in is configured.
You are signed out after you restart the browser.Your session is kept in memory only, on purpose. When the browser starts, the panel tries to sign you in again by itself, which works only while your organisation's sign-in session is still open. It does not try after you select Sign out.Select Sign in to QuantumOps in the panel.
The header says Not on a Halo page on a HaloPSA page.The page is not a ticket, client, user or agent record, or your HaloPSA is on a custom domain the browser has not allowed, or a browser policy blocks it.Open a record. For a custom domain, go to Halo URLs in Options, add the domain, accept the prompt and reload the HaloPSA tab. Then look for the domain under Granted origins, and select Re-check permissions. If the domain is listed and the panel still does not follow it, ask your administrator whether a policy blocks extensions on it.
The panel reports No tenant.The account you signed in with is not linked to a QuantumOps organisation.Sign in with the account you use for the QuantumOps web app, or ask your administrator.
Buttons that write are greyed out and a Read-only chip is showing.Your login is not linked to a HaloPSA agent.Ask your administrator to check your link in Team Management. Nothing needs reinstalling.
The live-updates dot is grey or amber, or Realtime hub is not connected.The live connection is blocked or down.The tabs still load when you open them. Switch tabs or records to refresh, and tell your administrator if it lasts.
Call, Clock or the dispatch board is missing.Your role, your organisation's modules or a switch on your instance does not allow it.See What each part of the extension needs.
The Chat tab shows Chat is not available on this server.Chat is not switched on for your instance.Use Qubit chat in the QuantumOps web app, and ask your administrator about the switch.
The Approvals tab says Tool approvals need the Administrator role.Only Administrators decide on tool approvals.Approvals for your own chat actions appear inside the Chat tab.
A banner says Update required and has no Later button.Your version is below the minimum your instance supports.Update the extension; see The QuantumOps browser extension.
Update now says your browser has not picked up the new version from the store yet.The store is ahead of your browser.Wait a few hours, or restart the browser. The browser installs the update by itself.
The Allow QuantumOps on prompt keeps coming back.The browser has not been given permission for that domain.Select Allow on and accept the browser's prompt. Not now puts it off for that domain.
Firefox says the add-on appears to be corrupt.Release Firefox refuses an unsigned add-on opened from the add-ons page. The file is not damaged.Load it as a temporary add-on instead; see The QuantumOps browser extension.
Firefox no longer has the extension after a restart.A temporary add-on is removed when Firefox closes.Load it again, or install from the Firefox Add-ons listing, which stays.
Edge shows a banner about sideloaded extensions.Expected when you load a bundle with Developer mode on.Ignore it, or install from a store.

Problems on the dispatch board itself, such as board notices, local mode, notifications and sounds, are covered in Board shortcuts, notices and troubleshooting.

Reload or reinstall the extension

After you replace the files of a bundle you loaded from a folder, select Reload on the extension's card in the browser's extensions page: chrome://extensions in Chrome or edge://extensions in Edge. In Firefox, load the new .xpi again. The extension keeps your instance address and custom HaloPSA domains, and you sign in again.

If reloading does not clear the problem, reinstall:

  1. Select Remove on the extension's card. This clears everything the extension stored: your instance address, your custom HaloPSA domains and any session.
  2. Install it again from a store or from a bundle.
  3. Set it up again; see Setting up the extension.

An extension your administrator installed by policy cannot be removed by you. Ask your administrator.

Tell your administrator or TechPulse support

A good report saves a round trip. Send:

  • the whole Diagnostics section, copied from Options;
  • the short organisation code from the panel's status bar;
  • what you selected, and what you expected to happen.

Your administrator can take it to TechPulse support; Getting help explains how.

Next steps