Object Not Found Matching Id:1, MethodName:update, ParamCount:4

Starting in April of 2024, lots of websites that use TrackJS (as well as other vendors) started getting large volumes of this error:, Object Not Found Matching Id:1, MethodName:update, ParamCount:4.

The Id number and ParamCount can vary depending on the website. But when it happens, it happens hundreds of times to the same user, which can be quite alarming.

Our JavaScript Errors Index explores symptoms, causes, and solutions to common JavaScript errors.

Understanding the error

The error message, Object Not Found Matching... is not a standard format from any browser or widely-adopted framework. So we have to do some digging.

Looking around on GitHub, the error format is used by the [CefSharp library], a .NET embedded Chromium tool. It’s the sort of thing a bot would use to crawl a website.

Here’s the specific line–it sure looks like our error!

Finding the root cause

The error is coming from a bot crawling your site. Should you be worried? Probably not.

There are lots of bots crawling public websites for all sorts of reasons: indexing content, discovering links, security checks, or training AI models.

Most likely though? One of the biggest users of CefSharp is Microsoft Outlook SafeSearch. It’s a tool used to scan links in emails to make sure they are not malicious. Someone probably emailed a link to your page to an Outlook user that scanned the link.

How to fix workaround

There is no user impact here, it’s just a bot :)

1. Ignore or exclude the error

You probably want to exclude this though to keep the noise down and make sure you notice real errors when they happen. If you use an error monitoring tool, add an exclusion or Ignore Rule for Object Not Found Matching Id.

If you can add more properties, it might be good to further restrict it to only Chromium browsers.

Here’s how you would do it in TrackJS, where you get unlimited server-side Ignore Rules. That means no code changes for you to make this happen!

2. Monitor Your Environment

Errors come from lots of different places on the web. Some are noise, but many will cause user problems and block your users. TrackJS can tell you when errors happen, and more importantly, how to fix them.