Tableau Feature Disruption

Deployment to the production environment has been completed. A final round of verification is underway.

We do not have an estimated time of completion; however, we will provide an update upon significant progress, or sooner if additional information becomes available.

We have successfully completed validations in the test environment, and deployment to the production environment is underway.

We do not have an estimated time of completion at this time; however, we will provide an update upon significant progress, or sooner if additional information becomes available.

We have deployed the fix in the test environment and are now testing it. Once testing is complete and we receive confirmation of the results, we will deploy it in the production environment.

We don’t have an estimated time of completion; however, we’ll provide an update upon significant update, or sooner if additional information becomes available.

Initial testing of the fix has been completed, and initial reports have indicated positive results. We are now deploying it to the test environment for further validations.

We don’t have an estimated time for the completion of all workstreams at this point; however, we’ll provide an update upon significant update, or sooner if additional information becomes available.

We’re continuing to work on resolving the issue. Deployment, testing, and validation are still underway.

We’ll provide another update upon the completion of testing of the fix or sooner if additional information becomes available.

We have identified a potential fix to the issue. We are now in the process of deploying and testing it in the Test environment. Deployment, testing, and validation are expected to take additional time.

We’ll provide another update upon the completion of testing of the fix or sooner if additional information becomes available.

We are aware of an issue affecting a subset of customers who may encounter failures while executing jobs using OAuth connections.

A recent release is the potential trigger of the issue, and we are evaluating if rolling back to the previous version will resolve the impact to customers.

We’ll provide an update upon significant update, or sooner if additional information becomes available.