Tableau Cloud Degradation

Tableau Engineers have confirmed that the solution put in place to mitigate the issue causing bridge errors in Caa, Dub01, EW1a, UKa, UE1, UEa, UEb, 10ay, 10az, and UW2b. was successful. This incident is now considered resolved.

Tableau Engineers have implemented a solution to mitigate the issue causing bridge errors in Caa, Dub01, EW1a, UKa, UE1, UEa, UEb, 10ay, 10az and UW2b. At this time, normal functionality has been restored, and we will continue to monitor the situation closely. Next update will be when new information becomes available.

Tableau Engineers have identified the cause of this issue. We are currently working to implement the fix to all Tableau Cloud users. We thank you for your patience; our next update will be when mitigation has been implemented.

While Tableau Engineers continue to investigate this issue, there is now a Knowledge Base article available with a workaround for users urgently seeking a solution.
https://kb.tableau.com/articles/issue/error-failed-to-launch-job-or-loading-data-sources-when-refreshing-tableau-bridge-data-sources

Tableau Engineers are continuing to investigate the bridge errors. Currently, the issue is believed to be related to the Daylight Savings Time change and only impacts a subset of data sources. We thank you for your patience; our next update will be when new information becomes available.

Tableau Engineers are continuing to investigate the bridge errors. We thank you for your patience; our next update will be when new information becomes available.

Tableau Engineers are investigating a potential bridge issue within 10ay, 10az, Ue1, Uea, Caa, Uw2b, and Ueb that may be causing an impact for our users. We are working to identify the scope of impact and implement a solution as quickly as possible. We thank you for your patience; our next update will be when new information becomes available.

Tableau Engineers are investigating a potential bridge issue within 10ay, 10az, ue1, CAa, Uw2b, and ueb that may be causing an impact for our users. We are working to identify the scope of impact and implement a solution as quickly as possible. We thank you for your patience; our next update will be when new information becomes available.