Service Health

This page provides status information on the services that are part of Google Cloud. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit https://cloud.google.com/.

Incident affecting Google Cloud Scheduler

Global: Cloud Scheduler Pub/Sub jobs fail with permission denied

Incident began at 2021-07-27 08:29 and ended at 2021-07-27 09:00 (all times are US/Pacific).

Date Time Description
28 Jul 2021 13:45 PDT

We apologize for the inconvenience this service disruption/outage may have caused. We would like to provide some information about this incident here: https://status.cloud.google.com/incidents/fEXXEicMtx5SaVZz2Gt7.

Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. If you have experienced impact outside of what is listed below, please reach out to Google Support by opening a case using https://cloud.google.com/support.

27 Jul 2021 09:00 PDT

The issue with Cloud Scheduler has been resolved for some projects as of Tuesday, 2021-07-27 08:59 US/Pacific.

We thank you for your patience while we worked on resolving the issue.

27 Jul 2021 08:56 PDT

Summary: Global: Cloud Scheduler Pub/Sub jobs fail with permission denied

Description: Mitigation work is currently underway by our engineering team.

We do not have an ETA for mitigation at this point.

We will provide more information by Tuesday, 2021-07-27 09:37 US/Pacific.

Diagnosis: Receiving Cloud Scheduler PERMISSION_DENIED

Workaround: Add publisher role to Cloud Scheduler service account. The service account has the form service-PROJECT_NUMBER@gcp-sa-cloudscheduler.iam.gserviceaccount.com

27 Jul 2021 08:29 PDT

Summary: Some Cloud Scheduler Pub/Sub jobs fail with permission denied

Description: We are experiencing an issue with Cloud Scheduler

Our engineering team continues to investigate the issue.

We will provide an update by Tuesday, 2021-07-27 09:00 US/Pacific with current details.

Diagnosis: None at this time.

Workaround: None at this time.