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.