When sending Algolia Insights events in the Google Chrome browser you may occasionally see warning messages referencing a Cross-Origin Read Blocking (CORB) issue.
The warning is due to the fact that the search-insights library sends the event with "nagivator.sendBeacon", a function that makes a request asynchronously without parsing the answer, and Chrome raises a CORB warning "when the response was going to be delivered to a context that can't handle it" (You can find more details on this in the Chromium docs here).
You can find a discussion on this topic in our Insights Github Repo here
The warning should not interfere with the events, if you do see problems with your events sending, there are steps you can take to validate your events.