Tableau Cloud incident

We've successfully validated the fix, which will be deployed via our regular release process. In the meantime, we are also developing a temporary workaround that affected customers can implement for i

Tableau Cloud is currently experiencing a minor incident affecting BRA2S and BRA54S and 1 more component, which began 10h ago. The vendor's full update timeline is below.

Started
Sep 01, 2026, 01:56 PM UTC
Resolved
Ongoing
Duration
● 9h 54m
Detected by Pingoru
Sep 01, 2026, 01:56 PM UTC

Affected components

BRA2SBRA54SBRA6SCAN2SCAN6SCAN70SCAN86SCHE26SCHE2SCS236

Update timeline

  1. identified Sep 01, 2026, 01:56 PM UTC

    Degradation Started: featurePerfDegradation

  2. monitoring Sep 01, 2026, 02:02 PM UTC

    We're investigating an issue where a subset of B2B Commerce Cloud customers may find that the Standard Coupon Code component is not visible on the Cart page following the recent release. As a result, guest users may be unable to view or use the Standard Coupon Code component. The issue is currently limited to sandbox environments. We're working to identify the cause and determine a resolution. We'll provide an update in 30 minutes or sooner as more information becomes available.

  3. monitoring Sep 01, 2026, 02:27 PM UTC

    We have identified a fix for the issue and are preparing it for testing. We'll validate the fix and work toward deploying it. We'll provide an update in 30 minutes or sooner as more information becomes available.

  4. monitoring Sep 01, 2026, 02:58 PM UTC

    We're preparing a test environment that replicates the conditions of the impacted sandbox environment. Once the environment is ready, we'll validate the fix against the issue and proceed with the next steps toward deployment. We'll provide an update in 60 minutes or sooner as more information becomes available.

  5. monitoring Sep 01, 2026, 03:46 PM UTC

    We're continuing to prepare and validate the fix for the issue affecting the Standard Coupon Code component in B2B Commerce Cloud sandbox environments. Once initial testing is complete, we'll progress the fix through additional validation before deployment. We'll provide an update in 3 hours or sooner as more information becomes available.

  6. monitoring Sep 01, 2026, 06:49 PM UTC

    We've successfully validated the fix, which will be deployed via our regular release process. In the meantime, we are also developing a temporary workaround that affected customers can implement for immediate relief. In parallel, we're investigating whether the issue may affect additional environments beyond the sandbox environments initially identified and are assessing the appropriate remediation path. We'll provide another update as significant progress is made.