Customers in us-central1 and asia-southeast2 may experience a delay in workflow progress
Sep 10, 20:51 UTCSep 11, 07:21 UTC
Duration
10h 30m
Impact
Major
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
us-central1asia-southeast2Google Cloud Provider (GCP) - us-central1Google Cloud Provider (GCP) - asia-southeast2
Final update
The environment has been validated and all residual issues have been cleared. This incident is now resolved.
Timeline
- Resolved · Sep 11, 07:21 UTC
The environment has been validated and all residual issues have been cleared. This incident is now resolved.
- Monitoring · Sep 11, 00:17 UTC
A configuration change affecting namespaces in the us-central1 and asia-southeast2 regions resulted in some workflow requests not being processed as expected. The change was rolled back and workflow processing resumed. We are continuing to validate the environment and clear any residual issues, and will provide further updates as that work completes.
- Monitoring · Sep 10, 23:29 UTC
We are continuing to monitor for any further issues.
- Monitoring · Sep 10, 22:59 UTC
While a small number of customer environments may still see some issues, mitigation has been in place and we continue to actively monitor.
- Monitoring · Sep 10, 22:29 UTC
We are continuing to monitor for any further issues.
- Monitoring · Sep 10, 22:27 UTC
The issue has been mitigated (as of 21:55 UTC) and we are actively monitoring the previously impacted environments.
- Identified · Sep 10, 20:51 UTC
Some customers with namespaces in the us-central1 and asia-southeast2 regions may experience errors and blocked progress on their workflows. We are currently rolling out a fix.
More from Temporal
Full historyNew namespace creation restricted across all GCP regionsstill openElevated latency and errors in GCP us-west1lasted 17mElevated latency and errors in AWS us-east-1lasted 2h 17mElevated error rates for cross-region traffic between US AWS regionslasted 0mElevated GCP storage latency in us-central1 – precautionary namespace failoverlasted 4h 25mIncreased errors on Temporal Cloud control plane, Cloud Ops API, and Temporal UIlasted 29m