Tableau Cloud incident
We completed rolling restarts across the initially impacted sandbox environments and cleared the cached database connections that retained the previous configurations. Apex test executions are now suc
Tableau Cloud experienced a minor incident on May 21, 2026 affecting BRA2S and BRA4S and 1 more component, lasting 11h 32m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 21, 2026, 04:11 PM UTC
Degradation Started: performanceDegradation
- monitoring May 21, 2026, 04:11 PM UTC
At 07:00 UTC, we noted a performance degradation impacting Apex test executions in some sandbox environments. At this time, some customers using SOQL queries with filters on External ID fields may experience test class failures due to no rows being returned during test execution. We’ll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring May 21, 2026, 04:54 PM UTC
We continue to investigate the issue impacting Apex test executions in some sandbox environments. Our engineering teams have identified a technical trigger and have developed a potential fix, which is currently undergoing validations. Once complete, we'll perform an expedited deployment to all impacted instances. We will provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring May 21, 2026, 05:34 PM UTC
Investigations have highlighted that the impact radius is broader than initially understood. We have updated the posting to reflect the additional instances experiencing impact, and customers in these instances will receive communications related to this incident going forward.
- monitoring May 21, 2026, 05:36 PM UTC
We continue to investigate the issue impacting Apex test executions in some sandbox environments. Ongoing validations of the current fix has shown some success, however we have also identified a potential regression. We are investigating this further to identify the cause. We will provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring May 21, 2026, 06:32 PM UTC
We continue to investigate the issue impacting Apex test executions in some sandbox environments. Ongoing investigation of the regression has identified additional changes which need to be reverted to its last known good configuration. The potential fix is currently underway and we will validate remediation once it's complete. We will provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring May 21, 2026, 07:43 PM UTC
We continue to investigate the issue impacting Apex test executions in some sandbox environments. The identified additional changes have been reverted to their last known good configuration, but impact still persists. We are investigating the issue and potential remediation solutions. We will provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring May 21, 2026, 09:03 PM UTC
We are currently deep-diving into system logs, attempting to reproduce the issue in isolation, and evaluating additional remediation options, including app server restart across all sandbox environments. We will provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring May 21, 2026, 09:59 PM UTC
We have completed a rolling restart of application servers to clear cached connection states; however, some customers continue to experience Apex test failures. We are actively collecting database traces and reviewing logs to determine the underlying technical cause and identify next steps. We will provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring May 21, 2026, 11:13 PM UTC
Further investigation indicates the continued customer failures are not related to this issue. The rolling restarts successfully released connections with pre-mitigation configurations. We are currently performing final validations and taking proactive actions to ensure full remediation. Some customers may observe Apex test executions are now succeeding. We will provide an update in 60 minutes or sooner if additional information becomes available.
- monitoring May 22, 2026, 12:23 AM UTC
We completed rolling restarts across the initially impacted sandbox environments and cleared the cached database connections that retained the previous configurations. Apex test executions are now succeeding for affected customers. As a proactive measure to ensure full remediation, we're currently performing a fleet-wide rolling restart across all remaining sandbox environments. We'll provide a final update upon the completion of these actions, or sooner if additional information becomes available.