Provider
Temporal CloudIncident detail
Self-Signup Onboarding Access Restriction
Timeline window
to
Get alerted the next time Temporal Cloud breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Resolved
Self-Signup onboarding was inadvertently restricted after a rollout, preventing users from completing Self-Signup onboarding.
The configuration change occurred on August 20 at 21:21 UTC, and the issue was noticed at approximately 12:40 UTC on August 21. The issue was mitigated at 13:01 UTC by correcting the onboarding configuration.
The onboarding configuration was corrected, and Self-Signup onboarding functionality has returned to normal.
Keep exploring
More from Temporal Cloud
Neighboring incidents on Temporal Cloud's timeline and the rest of their record on OutageDeck.
← Older incident
Customers in (GCP) us-west1 may experience elevated API latencies
Newer incident →
Elevated error rates in GCP us-central1
- Elevated error rates on Temporal Cloud Ops APIMinor
- Customers in us-east-1 may experience elevated latency in the Visibility APIMinor
- Some customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failuresMinor
- Intermittent request failures for some namespaces in GCP us-east4Minor