Some customer workflows started with FirstWorkflowTaskBackoff will have incorrect ExecutionDuration in their visibility record.
Incident Report for Temporal
Resolved
This incident has been resolved.
Posted Mar 08, 2024 - 05:55 UTC
Update
We are continuing to work on a fix for this issue.
Posted Mar 08, 2024 - 03:54 UTC
Identified
Some customer's workflows started with FirstWorkflowTaskBackoff will have incorrect ExecutionDuration in their visibility record. The fix is being deployed.
Posted Mar 08, 2024 - 03:54 UTC
This incident affected: us-east-1, us-west-2, ap-southeast-1, ap-southeast-2, eu-central-1, ca-central-1, eu-west-2, ap-northeast-1, eu-west-1, us-east-2, ap-south-1, sa-east-1, and ap-northeast-2.
← Current Status Powered by Atlassian Statuspage