Incidentsby IbisDegraded Child Workflow Execution
Apr 21, 23:15 UTCApr 21, 23:37 UTC
Duration
22m
Impact
Minor
Root cause
Not disclosed
Temporal, 90 days
27 incidents
Affected
Not listed by the vendor.
Final update
We identified and resolved an issue that caused some Child Workflows to fail to start under certain conditions. Affected Workflows have been reprocessed and are now operating normally as of 23:26 UTC.
Timeline
- Resolved · Apr 21, 23:37 UTC
We identified and resolved an issue that caused some Child Workflows to fail to start under certain conditions. Affected Workflows have been reprocessed and are now operating normally as of 23:26 UTC.
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