Temporal Status

This is still mitigated, and we are still monitoring. We have failed the namespaces back into their original location.

This is still mitigated, and we are monitoring. We will fail the namespaces back into the cell when we are confident it is healthy.

Some customers in AWS us-east-1 experienced a brief period of elevated latencies and unavailable responses between 17:45-18:08 UTC, and this has been resolved. We failed namespaces with MRN out of the cell. We are closely monitoring the situation, and we will fail the namespaces back into the cell when we are confident it is healthy.

This has been fixed, and the audit logs have been backfilled.

We have identified that audit logs have been temporarily delayed since approximately 2026-06-11 18:00:00 UTC. We are implementing a fix, and we expect no data loss and a completed backfill within hours.

Refresh operations across both open and closed workflows are complete in most regions; we continue to make steady progress across the remaining few namespaces in the us-east-1, us-west-2,  us-east4, us-west1, us-central1, asia-south1, europe-west3. No additional impact has been observed since mitigation was implemented, and we continue to closely monitor the environment. The next update will be provided once the refresh process has completed.

Refresh across open and closed workflows continues to progress smoothly. Once this is done, the incident will be resolved.

Refresh across open and closed workflows continues to progress smoothly. We're monitoring the situation and will post updates once complete.

As refresh of closed workflows progresses, some users may see unblocked stuck parent workflows from closed child workflows; this is happening because the missed task for closed child workflows is refreshed and delivered to parent. It could also happen on other stuck workflows that are waiting for task updates which were missed due to this incident.

We are continuing to monitor the ongoing refresh process for all open workflows. We are also considering options for refreshing closed workflows. We will continue to share more updates as this progresses.

Workflows will continue to be refreshed overnight, and we are monitoring the situation.

Workflows will continue to be refreshed overnight, and we are monitoring the situation.

Refreshes are still in progress and we are monitoring the situation.

Rollback is complete; refresh of open workflows is underway to unblock impacted workflows.

The rollback is making progress across impacted cells, and we are continuing to monitor the situation.

Rollback is still in progress and we are continuing to monitor the situation.

A bug in the recent update in History pagination caused a rare edge case where an extra task could be added before the response was returned. This incorrectly advanced the read level, causing some tasks to be skipped. We’ve identified the issue, and are currently rolling back the update to stop this from happening again. We will be refreshing all executions in cells where the update was deployed and will monitor these closely. This will progress any stuck workflows, but will not impact any of the closed ones.

We're rolling back the recent update as a possible mitigation to avoid any further occurrences of this issue. We are however still in the process of investigating root cause and will post updates as we have them.

We are investigating a recent update that could have caused intermittent missed task dispatches, resulting in some tasks being stuck. Impact identified as of now is limited to a handful of workflows that were caught in a rare edge case. We will continue to share more updates as investigation progresses.

We are continuing to investigate this issue. Please report any stuck workflows or activities to support so we can help unblock them as we work on root cause investigation and resolution.

We are investigating a few reports where a workflow or activity is becoming stuck and not making progress when it should. Please report any such issues you see to support.

We have identified the root cause and confirmed that no customer impact occurred.

We are investigating an issue that may result in delayed or incomplete data being returned by the Usage API for customers.

We are currently investigating this issue.

Some customers in AWS sa-east-1 may experience elevated API latencies. We are currently investigating the issue.

Some customers in us-west-2 may experience elevated rate of API errors & higher latencies