Tableau Cloud incident
A subset of customers who received the release continue to experience blank Business Manager pages due to a mismatch of the cache files. Manually clearing the cache is showing signs of recovery, and
Tableau Cloud experienced a minor incident on August 27, 2026 affecting POD313 and POD240 and 1 more component, lasting 1h 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Aug 27, 2026, 09:43 AM UTC
Degradation Started: featureServiceDisruption
- monitoring Aug 27, 2026, 09:57 AM UTC
We're investigating an issue where a subset of Commerce Cloud customers are unable to access Business Manager and are seeing a blank page due to a caching issue. This is causing a delay in invoicing and deadlines. Multiple teams have been engaged and are working to restore services. 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. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Aug 27, 2026, 10:23 AM UTC
Investigations indicate that rolling restarts following a recent release triggered the caching issue. We're manually clearing the cache to resolve the issue and customers are seeing signs of recovery. We'll continue clearing the cache for the remaining impacted PODs. Storefronts aren't impacted. We'll provide an update in 30 minutes or sooner if additional information becomes available.
- monitoring Aug 27, 2026, 10:58 AM UTC
A subset of customers who received the release continue to experience blank Business Manager pages due to a mismatch of the cache files. Manually clearing the cache is showing signs of recovery, and we continue to clear the cache to restore access to Business Manager. As a workaround, customers can manually clear the cache to restore access by following the steps outlined here: https://issues.salesforce.com/issue/a02g70000085e8H/ 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. We'll provide an update in 30 minutes or sooner if additional information becomes available.