If you have gauges that are not showing the needle (technically the needle is white):

• The solution we are offering is the Desktop App for MC 3.1.10 which implements a bug patch for all supported versions of MC. See also: Desktop App for MC- so much better than in a browser
• An alternative is to wait for an Accruent patch (not in the prerelease of MC 2026, but maybe will be in the final MC 2026, we'll update this when there is an Accruent fix available for on prem users)
• This can happen if you are running in a browser such as Edge, Brave or Chrome or any other browser.

This can happen if you are running our Desktop App for MC 3.1.9 or earlier, because we became aware of the bug after 3.1.9 shipped. 3 hours after we became aware of the bug we shipped 3.1.10 which inserted a fix for the Accruent bug.

Looking a little closer you can see the needle is white:

Technical details

Accruent is loading 'live'^?Loading live means, depending on caching, loading it each time it is needed instead of embedding it in the shipped code. So when changes you get the new version.

a library^?A library in this context is a set of code, usually written by a third party.

(Highcharts) they use from the owner's site instead of including the version that they tested with.

The site owner made a change it appears on June 11 2026 that breaks some MC users.

Specifically the needles on gauges turns white, it appears that they are missing.

The industry standard 'better' way to do this normally is to make a copy of the library and ship it with your product or link to a copy on your site, that way you are testing the version that customers are using. By downloading it live, it means any breaking changes can break your app. It also means if the provider goes out of business, all the old versions of your app are permanently broken.

The flip side argument is that it means when bugs are fixed by the library owner, you get the fixes. In this case, a library that changes only the style, we would have preferred if they used the method that locks it to a known version.

Testing alternate fixes in the browser can be difficult and require patience after each tweak.

It happens based on combinations of dark/light mode and theme of the OS or browser.

If you make changes to the theme or dark/light mode to try to fix it, be aware that testing has shown that those values are cached at various levels to avoid horrible performance problems (checking regularly) and it can take a couple days for your 'fixes' to percolate through.

You may be able to speed this up by rebooting your computer, which encourages the browser to refresh it's cache, but if not - be patient, your change in the browser will percolate through in a day or two.

Obviously, we recommend our proposed solution instead, using the Desktop App for MC 3.1.10 or newer, but if you want to try fixing it without that, be aware you may need to wait a couple days between each change to see whether it changed it or not, and this can make determining WHAT fixed it difficult since it could have been the change you made 2 days ago that fixed it, not the change you made 5 minutes ago.