Tableau Feature Degradation

We've successfully deployed the fix across all impacted instances. Currently monitoring system performance to ensure continued stability across all environments.

We'll provide the next update once validation is completed.

Upon further investigation, we've determined that the start time of the impact was different than initially understood. We've now 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're pleased to confirm that the fix has been successfully deployed to multiple PODs. We have updated the Trust post to reflect accurate timestamps for those PODs.
The remaining PODs are currently receiving the deployment. We will provide the next update once deployment is complete.

Following successful validation of the fix, deployment is now underway across all affected PODs.
We'll provide the next update once the production rollout is complete.

We continue to work with urgency on this issue, and are currently performing additional validation and testing of the fix to ensure service stability across all affected PODs before proceeding with the broader rollout.

We'll provide the next update once validation is complete and production deployment begins.

We have successfully deployed the fix-forward to our lower environment, and validation is currently underway. Following successful validation, we'll proceed with a staggered rollout to production environments throughout the day.

We'll provide the next update once validation is complete and production deployment begins.

Our teams continue to deploy remediation actions across the affected PODs. Once the deployment is complete, our teams will closely monitor telemetry and customer feedback to confirm that the issue is fully resolved. We expect that this may take up to 24 hours.

Thank you again for your patience. We’ll provide further updates on our progress as and when they become available.

Our teams have identified a recent change as the trigger, causing the extract refresh issues. We are developing a potential fix and are currently in the process of deploying remediation actions across the affected PODs. Once the deployment is complete, our teams will closely monitor telemetry and customer feedback to confirm that the issue is fully resolved.

Thank you again for your patience. We’ll provide further updates on our progress as and when they become available.

At 18:00 UTC, on March 24, we noted a degradation impacting the extract refresh jobs across multiple PODs. During this time, customers using SharePoint Lists JDBC for extract refreshes may experience failures when their OAuth connection expires. We're exploring multiple paths to isolate the underlying cause of the issue and implement a fix to restore the services.

We will provide an update in 60 minutes or sooner if additional information becomes available.