Tableau Cloud incident

Validation and testing of the authentication wait period was successful in our test environments. We will begin rolling this fix out during regional off-peak hours through a staggered approach across

Minor Resolved View vendor source →

Tableau Cloud experienced a minor incident on July 29, 2026 affecting USA9402 and EU54 and 1 more component, lasting 2d 20h. The incident has been resolved; the full update timeline is below.

Started
Jul 29, 2026, 08:51 AM UTC
Resolved
Aug 01, 2026, 05:17 AM UTC
Duration
2d 20h
Detected by Pingoru
Jul 29, 2026, 08:51 AM UTC

Affected components

USA9402EU54BRA2SBRA4SBRA54SBRA6SBRA8SCAN20SCAN2SCAN4S

Update timeline

  1. identified Jul 29, 2026, 08:51 AM UTC

    Degradation Started: featurePerfDegradation

  2. monitoring Jul 29, 2026, 08:51 AM UTC

    We’re aware that multiple customers are unable to export reports. When customers with the Report Export Transaction Security Policy enabled attempt to export a report, the system prompts them to complete identity verification. After they complete the verification, the export fails with an error. We've identified the trigger as a recent change and are working on a fix. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  3. monitoring Jul 29, 2026, 09:50 AM UTC

    We’ve identified a recent change as the trigger and are working to develop a fix-forward. An approval is in place for this fix forward. Once approved, the fix will be then tested for its effectiveness and deployed to the impacted instances to restore services. We'll provide an update in 30 minutes or sooner if additional information becomes available.

  4. monitoring Jul 29, 2026, 10:26 AM UTC

    We're currently testing the fix in a test environment to confirm the fix works as expected. Once testing is complete, the fix will be deployed to the impacted instances and is estimated to take several hours. We'll provide the next update upon a significant change or when more information becomes available.

  5. monitoring Jul 29, 2026, 10:41 AM UTC

    A Known Issue article, which includes an available workaround, can be found here: https://help.salesforce.com/s/issue?id=a02g7000006Yoa1AAC. Customers can apply the workaround to continue operations while the fix is being deployed. Note: If you've applied any workaround steps, please ensure they are reverted once the fix has been deployed. We'll provide the next update upon a significant change or when more information becomes available.

  6. monitoring Jul 29, 2026, 02:18 PM UTC

    Customers with the Transaction Security Policy enabled are experiencing a repeated authentication loop when exporting reports over 10,000 records, preventing exports from completing. This impacts production and sandbox environments, including Hyperforce and GovCloud, and is linked to a recent release. The fix is ready to be deployed to two test instances and is expected to take two hours to complete validations. Following successful validations, the fix will be deployed across all impacted instances. As a temporary workaround, customers can disable the Report Export Transaction Security Policy. If applied, please re-enable the policy once the fix is deployed. We’ll provide another update as additional information becomes available.

  7. monitoring Jul 29, 2026, 06:28 PM UTC

    The issue where report exports are triggering authentication loops for customers with Transaction Security Policies has been resolved for a subset of impacted instances. For full details on resolved instances, please visit the Trust post here: https://status.salesforce.com/incidents/20004310 Remediation is still actively in progress for the remaining impacted instances. We'll continue to provide updates as additional instances are restored.

  8. monitoring Jul 30, 2026, 06:41 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.

  9. monitoring Jul 30, 2026, 08:06 PM UTC

    While we previously indicated this issue would be resolved after deploying a fix, upon further investigation, we have identified additional underlying issues intermittently affecting report exports. We are actively investigating this further to resolve the issue as quickly as possible. We apologize for any confusion this may have caused and will continue to provide updates as more information becomes available.

  10. monitoring Jul 31, 2026, 04:32 AM UTC

    We have the initial fix deployed to a limited number of instances which did not fully resolve the issue. We identified two issues affecting report exports. Longer-running exports can fail due to repeated authentication prompts, and some exports may also intermittently need a retry to complete successfully. We're actively working on two mitigation efforts in parallel: A temporary configuration change to reduce immediate customer impact by letting longer exports complete, and a permanent fix for the underlying authentication flow, which we're developing and validating now. We'll continue to provide updates as more information becomes available.

  11. monitoring Jul 31, 2026, 09:37 AM UTC

    We continue to make progress on the report export issue. The temporary fix, which extends the authentication wait period to improve report export reliability, has been validated and will be deployed to a test environment before production rollout. The rollout will take some time to complete. In parallel, we continue to make progress on the permanent fix for the underlying authentication flow. We will continue to provide updates as more information becomes available.

  12. monitoring Jul 31, 2026, 06:36 PM UTC

    Validation and testing of the authentication wait period was successful in our test environments. We will begin rolling this fix out in a staggered manner across all impacted instances and follow the progress closely. This is expected to take several hours to fully complete, and we will provide updates to this post as the release develops. We will continue to provide updates as more information becomes available.