Standalone activities actions correction
Nov 15, 21:00 UTCNov 15, 21:00 UTC
Duration
0m
Impact
Informational
Root cause
Bug
Temporal, 90 days
21 incidents
Affected
Not listed by the vendor.
Final update
Due to a bug, some actions from Standalone Activities were not being counted towards APS since the feature was GA (September 15 2026). The fix impacts SAA start, reset, pause, and update-options actions and is being rolled out. This fix will be applied to all namespaces by November 19 2026. Impact: If you use Standalone Activities, you will notice an uptick in APS. Please reach out to support if you have any questions.
Timeline
- Resolved · Nov 15, 21:00 UTC
Due to a bug, some actions from Standalone Activities were not being counted towards APS since the feature was GA (September 15 2026). The fix impacts SAA start, reset, pause, and update-options actions and is being rolled out. This fix will be applied to all namespaces by November 19 2026. Impact: If you use Standalone Activities, you will notice an uptick in APS. Please reach out to support if you have any questions.
More from Temporal
Full historyElevated error rates on Temporal Cloud Ops APIlasted 0mCustomers in us-east-1 may experience elevated latency in the Visibility APIlasted 10h 53mSome customers connecting over AWS PrivateLink in us-west-2 might be experiencing connection failureslasted 3h 44mIntermittent request failures for some namespaces in GCP us-east4lasted 45mElevated connection resets for some GCP namespaceslasted 0mNew namespace creation restricted across few GCP regions. Impacted regions are us-central1 and europe-west3lasted 33d 3h