Around 14:30 UTC, November 17, a deployment done by our engineers to add more details to our logs caused jobs with timezones not to execute due to errors. The issue was discovered after almost 3 hours and took some time to revert.
In order to avoid this kind of issues in the future, we’ve added more alerts in the infrastructure that supports these jobs and added automation to our tests of jobs with timezones.