Run logs and artifacts missing for some runs (US Cell 3, GCP)

Final update

GCP has completed mitigations on their end that were causing some job runs to complete without their logs and artifacts (such as [manifest.json](https://manifest.json) and [run_results.json](https://run_results.json)) being available. Scheduled jobs and metadata ingestion have returned to their normal state and we are continuing to monitor.

1. Monitoring · Oct 8, 20:12 UTC
   GCP has completed mitigations on their end that were causing some job runs to complete without their logs and artifacts (such as [manifest.json](https://manifest.json) and [run_results.json](https://run_results.json)) being available. Scheduled jobs and metadata ingestion have returned to their normal state and we are continuing to monitor.
2. Investigating · Oct 8, 16:19 UTC
   We're investigating an issue with run artifact and log storage that is causing some job runs to complete without their logs and artifacts (such as manifest.json and run_results.json) being available. This is impacting some runs in the US Cell 3 (GCP) region anytime after 11:30 AM Eastern. The team is working on a resolution and we will provide updates at approximately 15 minute intervals or as soon as new information becomes available. Other dbt Cloud components are not impacted and should be running as expected. Job runs that use deferral and depend on artifacts from affected runs may fail.