This issue was due to a connection timeout to our background job datastore which was caused by a worker initialization issue. We've implemented a fix in manner that prevents this issue from reoccurring across all our services. We will also be implementing additional pre-deploy checks to further mitigate the occurrence of this scenario.
Posted 4 months ago. Apr 23, 2019 - 02:51 UTC
A fix has been implemented and we are monitoring the results.
Posted 4 months ago. Apr 22, 2019 - 18:54 UTC
Parallelized test runs that were scheduled for completion exhibited significant delays. We've implemented a temporary fix while we investigate the root cause.