Faulty deployment affecting all browser and multistep checks using playwright
Incident Report for Checkly

A faulty deployment added the globalTimeout Playwright configuration option. This option used an un-parsed environment variable set in our architecture, causing the timeout to be a string instead of a number.
For a subset of checks, Playwright failed with the following error: globalTimeout must be a non-negative number.

Due to a misconfiguration, the issue went undetected before reaching production. To mitigate and prevent this from happening again, we are leveraging our canary and test environments.

Posted May 30, 2024 - 13:45 UTC

This incident has been resolved.
Posted May 30, 2024 - 13:16 UTC
A fix has been implemented and we are monitoring the results.
Posted May 30, 2024 - 12:59 UTC
The issue has been identified and a fix is being implemented.
Posted May 30, 2024 - 12:56 UTC
We are continuing to investigate this issue.
Posted May 30, 2024 - 12:51 UTC
We are currently investigating this issue.
Posted May 30, 2024 - 12:50 UTC
This incident affected: Browser check runtime.