A fix was released regarding this issue, our parsing is now more forgiving and will allow invalid urls to be parsed without causing any side effects. The faulty request, prefixed by "Invalid URL:", will still be available in the network tab for a browser check result.
Posted Jun 27, 2022 - 14:36 UTC
Identified
We got some reports from our users that they see errors like "Cannot set property 'finishedAt' of undefined" or "ERR_INVALID_URL". After an investigation we identified that the issue happens with websites that have casalemedia.com integrated. During the check execution, we receive a URL that can't be parsed by NodeJS and this causes the errors. In order to avoid this, you can add the snippet below to your affected checks. We will make sure our parsing is more forgiving and the root cause of the failure is not polluted by our errors. await page.route('**/*', (route) => { return route.request().url().includes('casalemedia') ? route.abort() : route.continue() })