Tableau Cloud Outage History

We have resolved the issue causing authentication loops for customers with the Transaction Security Policy enabled during report exports. The issue was identified as a regression introduced in a recent release. We resolved it by deploying an updated release to the impacted instances. If you applied the temporary workaround and disabled the Report Export Transaction Security Policy, it is important that you re-enable this policy now that the fix has been deployed. We apologize for how this incident affected you and your business. We will undertake a full investigation of the incident, establishing the technical trigger, the underlying cause, and preventive action to avoid a repeat in the future.

The Salesforce Technology team has observed that instance stability and performance remain impacted following the implemented steps. Investigations will now resume to establish and assess an alternative best path forward. The next update will be provided in 30 minutes or sooner if information becomes available.

While we previously indicated this issue was resolved after deploying an update, 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. 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 continue to provide updates as more information becomes available.

We're aware of an issue affecting MuleSoft Anypoint Visualizer in the US region. Customers may be experiencing an inability to view metrics data and graphs. We're investigating the issue and will provide an update within 30 minutes or sooner if additional information becomes available.

We have identified that an accumulation of database logs is consuming storage and contributing to the elevated CPU usage. We are working to resolve this blockage to restore service as quickly as possible. We'll provide an update in 60 minutes or sooner if additional information becomes available.

As our investigation has progressed, we have identified a circular deadlock on the Visualizer database as an additional trigger for the elevated CPU. We are actively working to terminate the blocking sessions responsible for the deadlock. We'll provide an update in 60 minutes or sooner if additional information becomes available.

As a result of our remediation efforts, the database CPU has returned to normal levels and blocking sessions have been cleared. We are completing final steps to restore the Visualizer service. We also want to clarify the scope of impact: throughout this incident, the ability to view existing graphs was not affected. Only the metrics ingestion path was disrupted, meaning new metrics data may not have been recorded during the impact window. We'll provide an update in 60 minutes or sooner if additional information becomes available.

We're aware of an issue affecting email log retrieval for customers on a subset of instances. Customers are currently unable to retrieve email logs, as requests are taking too long to complete. We became aware of this issue at 11:00 UTC; customers have reported impact as early as 07:30 UTC. There's no workaround available at this time. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We're continuing to investigate an issue affecting email log retrieval for a subset of customers on impacted instances. Customers are experiencing timeout errors when attempting to retrieve email logs. We've updated the incident start time to 05:18 UTC based on the earliest identified impact. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've identified that internal automated search activity is consuming excessive resources, degrading the capacity available for this feature. We're actively working to address that activity and restore normal service. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We’re investigating the cause of the issue. We will provide an update in 30 minutes or sooner if we have more information.

We're aware of an issue on USA1274S where customers are experiencing complete disruption following a scheduled maintenance activity in their sandbox environment. We're working towards restoring services as quickly as possible. We'll provide another update in 30 minutes or sooner if additional information becomes available.

The sandbox instance failed to return to its original site after a scheduled activity was performed. We're working towards making a configuration change to allow the maintenance activity to complete successfully. We'll provide another update in 30 minutes or sooner if additional information becomes available.

We've identified an incorrect database configuration as the trigger for the failed scheduled maintenance activity. We're working towards a local restoration to resolve the configuration issue. We'll provide another update in 30 minutes or sooner if additional information becomes available.

We've removed the incorrect configuration entry and the local database restore process is now underway. The restoration is expected to take several hours, following which, the maintenance activity will be completed. We'll provide another update in 30 minutes or sooner if additional information becomes available.

The local database restore process is underway, and we’re monitoring the progress of the restore, which is expected to take several hours to complete, following which the maintenance activity is expected to resume. We'll provide the next update when there's a significant update or new information becomes available.

The local database restore is complete. We're now preparing to resume and complete the maintenance activity, which is expected to take several hours to complete. We'll provide the next update when there's a significant update or new information becomes available.

Our teams continue to investigate intermittent errors affecting customers' ability to view or apply policies in API Manager in the US region. We currently don’t have any updates to share at this time, but we will provide an update in 60 minutes or sooner if additional information becomes available.

Our teams continue to investigate the intermittent errors issue. We don’t have any new updates to share at this time, however we have not seen any errors in the last hour. We will provide an update when significant information becomes available.

We have identified and validated a fix in a test environment that resolved the issue and we did not observe any intermittent errors. We're now preparing to deploy this fix to the production environment. We'll provide an update when the fix has been fully deployed and validated or if significant information becomes available.

We're aware of an issue impacting the MuleSoft EU production environment, causing intermittent errors. Users may experience deployment failures, errors when checking deployment status, and slow or degraded platform services. We're investigating the issue and will provide an update in 60 minutes or sooner if additional information becomes available.

We've identified the trigger for this issue and are currently implementing measures to restore normal service. We'll provide an update in 60 minutes or sooner if additional information becomes available.

We've completed a configuration change to remove a rate-limit bypass that was contributing to elevated authentication requests. We're continuing to execute additional measures to restore normal service. We'll provide an update in 60 minutes or sooner if additional information becomes available.

We're continuing to execute additional measures to restore normal service, including rebalancing authentication service capacity. We'll provide an update in 60 minutes or sooner if additional information becomes available.

We're aware of an issue affecting Agentforce Voice where users may experience intermittent failures when the voice agent doesn't capture or respond to input after the initial greeting, preventing completion of voice-based interactions. We identified the issue as being related to a connection failure between the voice service and its speech processing component. We're preparing a fix for deployment. We'll provide an update in 90 minutes or sooner if additional information becomes available.

A fix has been prepared and deployment is currently in progress for the impacted environments. We'll monitor service restoration and provide an update in 60 minutes or sooner if additional information becomes available.

We have deployed a fix and are monitoring service restoration; the early signals are positive. We'll provide an update in 60 minutes or sooner if additional information becomes available.

We're aware of an issue affecting Runtime Manager on Anypoint Management Center. Customers in the US region are unable to view their application list in the Runtime Manager UI. Customers can use the Command Line Interface (CLI) as a workaround to manage their applications while we investigate. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We’ve implemented a solution to resolve the issue causing the feature degradation. Initial results indicate that the feature is working as expected. Engineers continue to monitor the situation closely. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

We're investigating automation query delays where customers are experiencing longer than expected run times for individual queries or queries failing within Automation Studio. Multiple teams have been engaged to assist with the investigation. Upon further investigation, we've determined that the start time of impact is different than initially understood. We've revised the start time of the Trust post to more accurately reflect the time customers may have begun to experience impact. We apologize for any confusion caused by this. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We continue to investigate automation query delays and delays in task pickup within Automation Studio. Investigations indicate a capacity issue that's triggering these delays or failures. We're actively engaged in investigating the cause and we apologize for any inconvenience this issue is causing. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Customers continue to experience longer than expected run times or queries failing within Automation Studio. We're working on resolving the capacity issue and restoring normal operations. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Remediation efforts are underway to resolve the delays and failures in query execution in Automation Studio. We apologize for any inconvenience this issue is causing. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We’re investigating an issue impacting the Tableau Public site where customers may encounter a maintenance page, HTTP 502 errors, or request timeouts when attempting to access the site. The impact is currently limited to Tableau Public site. We’re investigating the cause of the issue and working to restore normal service. We've confirmed that the incident start time is earlier than initially reported and have updated this Trust post to reflect the correct start time. We will provide an update in 30 minutes or sooner if new information becomes available.

We continue to investigate the issue impacting the Tableau Public site. We've implemented few changes and are monitoring the service to evaluate their effectiveness. Although the site may load intermittently, published content and related services may remain unavailable. We will provide another update in 60 minutes or sooner if new information becomes available.

We're seeing improved service stability following the changes we've implemented and are continuing to monitor the service. While Tableau public site is accessible, some customers may still experience intermittent issues accessing published content and related services. We will provide another update in 60 minutes or sooner if new information becomes available.

We're aware of an issue at the network tier impacting multiple production instances. Services affected include Einstein Activity Capture and Conversation Intelligence. Customers using these services may experience failures, errors, or delays. The issue is under active investigation. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've identified an infrastructure configuration change as the trigger. We're rolling back that change and will complete the necessary validation and verification following the rollback. Our investigation has revealed that the impact is broader than initially understood, and the affected services now include Marketing Cloud Engagement. Additional instances have been identified as impacted, and customers on these instances will receive communications about this incident. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Our investigation has confirmed that a subset of customers may experience issues with MuleSoft and Marketing Cloud Engagement services. We're continuing to roll back the infrastructure change that triggered the issue. We've successfully restored and validated one production environment, and we're now executing rollbacks in parallel across the remaining affected production instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.

Customers may experience delays or errors when accessing the affected services while the rollback is in progress. We're rolling back the infrastructure change across all affected production instances, and we're validating the instances where the rollback is already complete. We expect the rollback to be complete in approximately 90 minutes. We'll provide an update once the rollback is complete across all impacted production instances, or sooner if we have more information.

We have identified additional instances experiencing this issue, Customers on these newly identified instances will receive communications about this incident. Multiple regions have already recovered following the rollback action, and remediation continues on those remaining. We'll provide an update once the rollback is complete across all impacted production instances, or sooner if we have more information.

We are investigating an issue where customers are unable to place orders due to an error message at checkout. Investigations have identified a recent release as the primary cause, and our teams have started the process to roll this release back to a known good state. Engineering teams are noting that error rates are also returning to normal levels, and some affected storefronts may be seeing recovery. Teams are actively monitoring the rollback status as well as the B2C Commerce Cloud environment to confirm service restoration. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We have completed the rollback of the recent release. We have observed that order flow has returned to normal levels across the majority of impacted storefronts. Our teams are actively monitoring the environment to confirm full service restoration for the remaining affected instances. We'll provide an update in 30 minutes or sooner if additional information becomes available.

During our validations, we’ve identified one specific environment that continues to experience errors. We are actively investigating and working to fully restore services. We'll provide an update once additional information becomes available.

On July 8 at 17:00 UTC, we became aware of an issue where customers may observe an Agentforce icon in Sandbox and Production environments even when the Agentforce Default Agent setting is disabled. Our investigation has confirmed this is the Small Business Suites Employee Assistance agent, which is enabled by design for eligible organizations with Foundation. There is currently no organization-level option to disable or hide this agent. We are developing a fix and will provide another update as more information becomes available. For additional information, please refer to our Help article: https://help.salesforce.com/s/issue?id=a02g7000005ohtJ

We have completed development of the fix and have begun deploying it across affected environments. For additional information, please refer to our Help article: https://help.salesforce.com/s/issue?id=a02g7000005ohtJ We will provide an update when the deployment is complete or if additional information becomes available.

We continue to deploy the fix across affected environments. As we implement these changes, users may experience brief periods of degraded performance. This behavior is expected and will resolve automatically once the process is complete. We are monitoring our systems closely to ensure minimal impact to your business. We apologize for this inconvenience. We will provide an update when the deployment is complete or if additional information becomes available.

The fix is continuing to be deployed across all affected environments. We will provide an update when the deployment is complete or if additional information becomes available.

We're aware that some customers are unable to log into their sandbox environments due to unexpected multi-factor authentication (MFA) prompts, despite having MFA exemptions configured. We’ve identified that a recent change is enforcing MFA and passkey verification and we’re preparing a rollback to restore services. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We've started rolling back the recent change and are monitoring the system to verify that expected login behavior is restored. We’ve also identified a few additional impacted instances, and those have now been included in the Trust post. Customers on those instances will receive notifications going forward. We're continuing to identify any other impacted instances and we'll provide an update in 30 minutes or sooner if additional information becomes available.

Some customers are experiencing issues logging into the Anypoint Platform via single-sign-on. We're aware of the issue and are actively investigating. We'll provide an update in 30 minutes or sooner if additional information becomes available.

We’ve identified the issue and are proceeding to roll back a configuration change we believe is the cause. This should take no longer than approximately 30 minutes to complete. We will provide additional information as new details become available. We apologize for any inconvenience this issue is causing to customers.