Recent Notices for Tableau Online

RESOLVED: EU-West-1A Connections Degraded

12:00 AM PDT - 6/15/2018 to 9:50 AM PDT - 6/15/2018
Published on: Friday June 15th, 2018 - 9:12 AM PDT

Resolved 4:50pm UTC: Our engineers have successfully resolved the Redshift and Athena connection issue. Connections to these data sources are now fully functional and accessible. We now consider this issue resolved.

=========

Engineers have identified a connection issue in the EU-West-1A environment. During this time connections to Redshift and Athena data sources are unavailable. The appropriate team is engaged and is actively working on resolving this behavior.

Next update Friday, June 15th at 5:00pm UTC

RESOLVED: Tableau Online Extract Refreshes Degraded

12:00 AM PDT - 6/11/2018 to 9:04 PM PDT - 6/11/2018
Published on: Sunday June 10th, 2018 - 10:14 PM PDT

Resolved 4:04am UTC: The engineering team has completed deploying the code fix to the dub01 pod, bringing it back into a healthy state. Functionality has been restored and we are closely monitoring the environment. This issue is now being considered resolved.

=========

Update 12:00am UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We are currently deploying the fix un the Dub01 environment. We will update once this deployment is complete.

Next update will be Tuesday, June 12th at 4am UTC

=========

Update 8:00pm UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We will be deploying this fix today and will post an update when the deployment is complete.

Next update will be Tuesday, June 12th at 12am UTC

=========

Update 7:00pm UTC Our engineering team is hard at work troubleshooting the issues that surfaced during the testing and validation steps. To reduce long pending wait times for extract refreshes, the team has deployed extra resources to the Dub01 environment. Users will see reduced wait times to initiate extract refreshes, but refreshes will continue to take up to 50% longer than normal to finish executing. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge.

Next update will be at Monday, June 11th at 8pm UTC

=========

Update 7:00pm UTC Our engineers have successfully created a build with the necessary changes. Additionally, the team is working to add additional capacity to the current environment to help alleviate long wait times for extract refreshes. During the testing and validation process for the new build, the team has identified an issue that will delay the originally intended resolution date of Monday 6/11. Users who are receiving timeout errors with extract refreshes should schedule extract refreshes with Tableau Bridge in the meantime.

Next update will be at June 8th, at 7pm UTC

=========

Update 1:00am UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 7pm UTC

=========

Update 8:00pm UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 1am UTC

=========

Update 7:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 8:30pm UTC

=========

Update 6:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 7:30pm UTC

=========

Engineers are currently investigating an issue with extracts taking a long time to refresh. At this time users may encounter time out error or see extracts in a pending status for a long period of time.

Next update at 6:30pm UTC

RESOLVED: Tableau Online Extract Refreshes Degraded

12:00 AM PDT - 6/10/2018 to 9:04 PM PDT - 6/11/2018
Published on: Sunday June 10th, 2018 - 1:06 PM PDT

Resolved 4:04am UTC: The engineering team has completed deploying the code fix to the dub01 pod, bringing it back into a healthy state. Functionality has been restored and we are closely monitoring the environment. This issue is now being considered resolved.

=========

Update 12:00am UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We are currently deploying the fix un the Dub01 environment. We will update once this deployment is complete.

Next update will be Tuesday, June 12th at 4am UTC

=========

Update 8:00pm UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We will be deploying this fix today and will post an update when the deployment is complete.

Next update will be Tuesday, June 12th at 12am UTC

=========

Update 7:00pm UTC Our engineering team is hard at work troubleshooting the issues that surfaced during the testing and validation steps. To reduce long pending wait times for extract refreshes, the team has deployed extra resources to the Dub01 environment. Users will see reduced wait times to initiate extract refreshes, but refreshes will continue to take up to 50% longer than normal to finish executing. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge.

Next update will be at Monday, June 11th at 8pm UTC

=========

Update 7:00pm UTC Our engineers have successfully created a build with the necessary changes. Additionally, the team is working to add additional capacity to the current environment to help alleviate long wait times for extract refreshes. During the testing and validation process for the new build, the team has identified an issue that will delay the originally intended resolution date of Monday 6/11. Users who are receiving timeout errors with extract refreshes should schedule extract refreshes with Tableau Bridge in the meantime.

Next update will be at June 8th, at 7pm UTC

=========

Update 1:00am UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 7pm UTC

=========

Update 8:00pm UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 1am UTC

=========

Update 7:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 8:30pm UTC

=========

Update 6:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 7:30pm UTC

=========

Engineers are currently investigating an issue with extracts taking a long time to refresh. At this time users may encounter time out error or see extracts in a pending status for a long period of time.

Next update at 6:30pm UTC

RESOLVED: Tableau Online Extract Refreshes Degraded

12:00 AM PDT - 6/9/2018 to 9:04 PM PDT - 6/11/2018
Published on: Saturday June 9th, 2018 - 5:14 AM PDT

Resolved 4:04am UTC: The engineering team has completed deploying the code fix to the dub01 pod, bringing it back into a healthy state. Functionality has been restored and we are closely monitoring the environment. This issue is now being considered resolved.

=========

Update 12:00am UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We are currently deploying the fix un the Dub01 environment. We will update once this deployment is complete.

Next update will be Tuesday, June 12th at 4am UTC

=========

Update 8:00pm UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We will be deploying this fix today and will post an update when the deployment is complete.

Next update will be Tuesday, June 12th at 12am UTC

=========

Update 7:00pm UTC Our engineering team is hard at work troubleshooting the issues that surfaced during the testing and validation steps. To reduce long pending wait times for extract refreshes, the team has deployed extra resources to the Dub01 environment. Users will see reduced wait times to initiate extract refreshes, but refreshes will continue to take up to 50% longer than normal to finish executing. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge.

Next update will be at Monday, June 11th at 8pm UTC

=========

Update 7:00pm UTC Our engineers have successfully created a build with the necessary changes. Additionally, the team is working to add additional capacity to the current environment to help alleviate long wait times for extract refreshes. During the testing and validation process for the new build, the team has identified an issue that will delay the originally intended resolution date of Monday 6/11. Users who are receiving timeout errors with extract refreshes should schedule extract refreshes with Tableau Bridge in the meantime.

Next update will be at June 8th, at 7pm UTC

=========

Update 1:00am UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 7pm UTC

=========

Update 8:00pm UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 1am UTC

=========

Update 7:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 8:30pm UTC

=========

Update 6:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 7:30pm UTC

=========

Engineers are currently investigating an issue with extracts taking a long time to refresh. At this time users may encounter time out error or see extracts in a pending status for a long period of time.

Next update at 6:30pm UTC

RESOLVED: Tableau Online Extract Refreshes Degraded

12:00 AM PDT - 6/8/2018 to 5:40 PM PDT - 6/8/2018
Published on: Friday June 8th, 2018 - 5:55 PM PDT

Resolved 12:40am UTC:

The engineering team has also completed deploying the code fix to the 10az pod, bringing it back into a healthy state. Functionality has been restored and we are closely monitoring the environment. This issue is now being considered resolved.

=========

Update 7:00pm UTC Our engineering team will be deploying the code fix to the 10ay and 10az environments today. We will post an update when the deployment is complete.

Next update Saturday June 9th at 1:00am UTC

=========

Update 7:00pm UTC Our engineers have successfully created a build with the necessary changes. Additionally, the team has added additional capacity to the current environment to help alleviate long wait times for extract refreshes. At this time, the team is going through the testing and validating process for the new build and expects to remain on track for release. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge.

Next update will be at June 8th, 7pm UTC

=========

Update 1:00am UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Friday, 6/8. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 7pm UTC

=========

Update 8:00pm UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Friday, 6/8. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 1am UTC

=========

Update 7:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 8:30pm UTC

=========

Update 6:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 7:30pm UTC

=========

Engineers are currently investigating an issue with extracts taking a long time to refresh. At this time users may encounter time out error or see extracts in a pending status for a long period of time.

Next update at 6:30pm UTC

RESOLVED: Tableau Online Extract Refreshes Degraded

12:00 AM PDT - 6/8/2018 to 5:00 PM PDT - 6/8/2018
Published on: Friday June 8th, 2018 - 5:57 PM PDT

Resolved 12:00am UTC:

The engineering team has completed deploying the code fix to the 10ay pod, bringing it back into a healthy state. Functionality has been restored and we are closely monitoring the environment. This issue is now being considered resolved.

=========

Update 7:00pm UTC Our engineering team will be deploying the code fix to the 10ay and 10az environments today. We will post an update when the deployment is complete.

Next update Saturday June 9th at 1:00am UTC

=========

Update 7:00pm UTC Our engineers have successfully created a build with the necessary changes. Additionally, the team has added additional capacity to the current environment to help alleviate long wait times for extract refreshes. At this time, the team is going through the testing and validating process for the new build and expects to remain on track for release. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge.

Next update will be at June 8th, 7pm UTC

=========

Update 1:00am UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Friday, 6/8. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 7pm UTC

=========

Update 8:00pm UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Friday, 6/8. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 1am UTC

=========

Update 7:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 8:30pm UTC

=========

Update 6:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 7:30pm UTC

=========

Engineers are currently investigating an issue with extracts taking a long time to refresh. At this time users may encounter time out error or see extracts in a pending status for a long period of time.

Next update at 6:30pm UTC

RESOLVED: Tableau Online Extract Refreshes Degraded

12:00 AM PDT - 6/8/2018 to 9:04 PM PDT - 6/11/2018
Published on: Thursday June 7th, 2018 - 10:09 PM PDT

Resolved 4:04am UTC: The engineering team has completed deploying the code fix to the dub01 pod, bringing it back into a healthy state. Functionality has been restored and we are closely monitoring the environment. This issue is now being considered resolved.

=========

Update 12:00am UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We are currently deploying the fix un the Dub01 environment. We will update once this deployment is complete.

Next update will be Tuesday, June 12th at 4am UTC

=========

Update 8:00pm UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We will be deploying this fix today and will post an update when the deployment is complete.

Next update will be Tuesday, June 12th at 12am UTC

=========

Update 7:00pm UTC Our engineering team is hard at work troubleshooting the issues that surfaced during the testing and validation steps. To reduce long pending wait times for extract refreshes, the team has deployed extra resources to the Dub01 environment. Users will see reduced wait times to initiate extract refreshes, but refreshes will continue to take up to 50% longer than normal to finish executing. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge.

Next update will be at Monday, June 11th at 8pm UTC

=========

Update 7:00pm UTC Our engineers have successfully created a build with the necessary changes. Additionally, the team is working to add additional capacity to the current environment to help alleviate long wait times for extract refreshes. During the testing and validation process for the new build, the team has identified an issue that will delay the originally intended resolution date of Monday 6/11. Users who are receiving timeout errors with extract refreshes should schedule extract refreshes with Tableau Bridge in the meantime.

Next update will be at June 8th, at 7pm UTC

=========

Update 1:00am UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 7pm UTC

=========

Update 8:00pm UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 1am UTC

=========

Update 7:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 8:30pm UTC

=========

Update 6:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 7:30pm UTC

=========

Engineers are currently investigating an issue with extracts taking a long time to refresh. At this time users may encounter time out error or see extracts in a pending status for a long period of time.

Next update at 6:30pm UTC

RESOLVED: Tableau Online Extract Refreshes Degraded

12:00 AM PDT - 6/7/2018 to 5:40 PM PDT - 6/8/2018
Published on: Thursday June 7th, 2018 - 2:20 AM PDT

Resolved 12:40am UTC:

The engineering team has also completed deploying the code fix to the 10az pod, bringing it back into a healthy state. Functionality has been restored and we are closely monitoring the environment. This issue is now being considered resolved.

=========
Update 7:00pm UTC Our engineering team will be deploying the code fix to the 10ay and 10az environments today. We will post an update when the deployment is complete.

Next update Saturday June 9th at 1:00am UTC

=========

Update 7:00pm UTC Our engineers have successfully created a build with the necessary changes. Additionally, the team has added additional capacity to the current environment to help alleviate long wait times for extract refreshes. At this time, the team is going through the testing and validating process for the new build and expects to remain on track for release. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge.

Next update will be at June 8th, 7pm UTC

=========

Update 1:00am UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Friday, 6/8. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 7pm UTC

=========

Update 8:00pm UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Friday, 6/8. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 1am UTC

=========

Update 7:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 8:30pm UTC

=========

Update 6:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 7:30pm UTC

=========

Engineers are currently investigating an issue with extracts taking a long time to refresh. At this time users may encounter time out error or see extracts in a pending status for a long period of time.

Next update at 6:30pm UTC

RESOLVED: Tableau Online Extract Refreshes Degraded

12:00 AM PDT - 6/7/2018 to 9:04 PM PDT - 6/11/2018
Published on: Thursday June 7th, 2018 - 2:21 AM PDT

Resolved 4:04am UTC: The engineering team has completed deploying the code fix to the dub01 pod, bringing it back into a healthy state. Functionality has been restored and we are closely monitoring the environment. This issue is now being considered resolved.

=========

Update 12:00am UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We are currently deploying the fix un the Dub01 environment. We will update once this deployment is complete.

Next update will be Tuesday, June 12th at 4am UTC

=========

Update 8:00pm UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We will be deploying this fix today and will post an update when the deployment is complete.

Next update will be Tuesday, June 12th at 12am UTC

=========

Update 7:00pm UTC Our engineering team is hard at work troubleshooting the issues that surfaced during the testing and validation steps. To reduce long pending wait times for extract refreshes, the team has deployed extra resources to the Dub01 environment. Users will see reduced wait times to initiate extract refreshes, but refreshes will continue to take up to 50% longer than normal to finish executing. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge.

Next update will be at Monday, June 11th at 8pm UTC

=========

Update 7:00pm UTC Our engineers have successfully created a build with the necessary changes. Additionally, the team is working to add additional capacity to the current environment to help alleviate long wait times for extract refreshes. During the testing and validation process for the new build, the team has identified an issue that will delay the originally intended resolution date of Monday 6/11. Users who are receiving timeout errors with extract refreshes should schedule extract refreshes with Tableau Bridge in the meantime.

Next update will be at June 8th, at 7pm UTC

=========

Update 1:00am UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 7pm UTC

=========

Update 8:00pm UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 1am UTC

=========

Update 7:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 8:30pm UTC

=========

Update 6:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 7:30pm UTC

=========

Engineers are currently investigating an issue with extracts taking a long time to refresh. At this time users may encounter time out error or see extracts in a pending status for a long period of time.

Next update at 6:30pm UTC

No incidents in the last 30 days in US-East-1

12:01 AM PDT - 6/6/2018
Published on: Wednesday June 6th, 2018 - 8:40 AM PDT

No incidents in the last 30 days.

RESOLVED: Tableau Online Extract Refreshes Degraded

12:00 AM PDT - 6/6/2018 to 5:40 PM PDT - 6/8/2018
Published on: Wednesday June 6th, 2018 - 10:23 AM PDT

Resolved 12:40am UTC:

The engineering team has also completed deploying the code fix to the 10az pod, bringing it back into a healthy state. Functionality has been restored and we are closely monitoring the environment. This issue is now being considered resolved.

=========

Update 7:00pm UTC Our engineering team will be deploying the code fix to the 10ay and 10az environments today. We will post an update when the deployment is complete.

Next update Saturday, June 9th at 1:00am UTC

=========

Update 7:00pm UTC Our engineers have successfully created a build with the necessary changes. Additionally, the team has added additional capacity to the current environment to help alleviate long wait times for extract refreshes. At this time, the team is going through the testing and validating process for the new build and expects to remain on track for release. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge.

Next update will be at June 8th, 7pm UTC

=========

Update 1:00am UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Friday, 6/8. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 7pm UTC

=========

Update 8:00pm UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Friday, 6/8. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 1am UTC

=========

Update 7:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 8:30pm UTC

=========

Update 6:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 7:30pm UTC

=========

Engineers are currently investigating an issue with extracts taking a long time to refresh. At this time users may encounter time out error or see extracts in a pending status for a long period of time.

Next update at 6:30pm UTC

RESOLVED: Tableau Online Extract Refreshes Degraded

12:00 AM PDT - 6/6/2018 to 9:04 PM PDT - 6/11/2018
Published on: Wednesday June 6th, 2018 - 10:30 AM PDT

Resolved 4:04am UTC: The engineering team has completed deploying the code fix to the dub01 pod, bringing it back into a healthy state. Functionality has been restored and we are closely monitoring the environment. This issue is now being considered resolved.

=========

Update 12:00am UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We are currently deploying the fix un the Dub01 environment. We will update once this deployment is complete.

Next update will be Tuesday, June 12th at 4am UTC

=========

Update 8:00pm UTC Our engineering team has tested and validated a fix for the Dub01 environment that will address the extract refresh issue. We will be deploying this fix today and will post an update when the deployment is complete.

Next update will be Tuesday, June 12th at 12am UTC

=========

Update 7:00pm UTC Our engineering team is hard at work troubleshooting the issues that surfaced during the testing and validation steps. To reduce long pending wait times for extract refreshes, the team has deployed extra resources to the Dub01 environment. Users will see reduced wait times to initiate extract refreshes, but refreshes will continue to take up to 50% longer than normal to finish executing. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge.

Next update will be at Monday, June 11th at 8pm UTC

=========

Update 7:00pm UTC Our engineers have successfully created a build with the necessary changes. Additionally, the team is working to add additional capacity to the current environment to help alleviate long wait times for extract refreshes. During the testing and validation process for the new build, the team has identified an issue that will delay the originally intended resolution date of Monday 6/11. Users who are receiving timeout errors with extract refreshes should schedule extract refreshes with Tableau Bridge in the meantime.

Next update will be at June 8th, at 7pm UTC

=========

Update 1:00am UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 7pm UTC

=========

Update 8:00pm UTC Engineers have identified the source of the issue. During this time, all extract refreshes in will take up to 50% longer than normal to execute. Engineers are working on implementing a solution. The resolution will require a code fix which needs to pass testing and validation steps before it can be implemented. Due to all the moving parts that go into a deployment, we expect to have this issue tested, validated, and fully resolved by Monday, 6/11. To work around this issue in the meantime, affected users should schedule extract refreshes with Tableau Bridge

Next update will be at June 7th, 1am UTC

=========

Update 7:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 8:30pm UTC

=========

Update 6:30pm UTC Engineers are continuing to investigate the extract refresh issues occurring in the 10ay, 10az, and Dub01 environments. Thank you for your patience while we work to bring these environments back into a healthy state.

Next update will be at 7:30pm UTC

=========

Engineers are currently investigating an issue with extracts taking a long time to refresh. At this time users may encounter time out error or see extracts in a pending status for a long period of time.

Next update at 6:30pm UTC

RESOLVED: Degradation | Tableau Online 10AY Environment

6:19 AM PDT - 6/4/2018 to 10:00 AM PDT - 6/4/2018
Published on: Monday June 4th, 2018 - 6:19 AM PDT

Resolved 17:00pm UTC The extract refresh failures scope is limited to a low number of customers. Tableau engineers are working directly with those customers. At this time, we are considering the issue resolved.

=========

Update 16:00pm UTC Tableau Engineers are continuing to narrow down the root cause of refresh extract task failures. The team is engaged and working towards a resolution. Thank you for your patience at this time.

Next update will be at 17:00 UTC

=========

Update 15:00pm UTC Tableau Online is currently in a degraded state. During this time, when running a refresh extract task on Tableau Online (10AY), users may experience an Amazon Redshift error. Initial reports indicate that the problem began over the weekend of 6/2. Engineers have been notified and are actively engaged in determining the root cause of the issue and are working towards implementing a solution.
Thank you for your patience at this time.

Next update will be at 16:00 UTC

=========

Update 14:00pm UTC Tableau Online is currently in a degraded state. During this time, when running a refresh extract task on Tableau Online (10AY), users may experience an Amazon Redshift error. Initial reports indicate that the problem began over the weekend of 6/2. Engineers have been notified and are actively engaged in determining the root cause of the issue and are working towards implementing a solution.
Thank you for your patience at this time.

Next update will be at 15:00 UTC

=========

Tableau Online is currently in a degraded state. During this time, when running a refresh extract task on Tableau Online (10AY), users may experience an Amazon Redshift error. Initial reports indicate that the problem initially began over the weekend of 6/2. Engineers have been notified and are actively engaged in determining the root cause of the issue and are working towards implementing a solution.

Next update at 14:00 PM UTC

Maintenance – Tableau Online UW2B environment

10:00 PM PDT - 6/2/2018 to 12:00 AM PDT - 6/3/2018
Published on: Friday May 18th, 2018 - 1:46 AM PDT

Update 3:45pm PT:

The maintenance activity posted previously has been rescheduled due to some technical issues. Here is the updated schedule:

On Sunday, June 3, 2018 from 5:00am UTC to 7:00am UTC, the Tableau Online US-WEST-2A environment may be unavailable due to a third-party vendor’s need to perform maintenance to their infrastructure. During this time, users may be unable to access the US-WEST-2A environment for a period of up to ~2 minutes within the maintenance window provided. Updates will be posted to Trust if new information becomes available.

------------------

On Sunday, May 27th, 2018 from 5:00am UTC to 7:00am UTC, the Tableau Online US-WEST-2B environment may be unavailable due to a third-party vendor’s need to perform maintenance to their infrastructure. During this time, users may be unable to access the US-WEST-2B environment for a period of up to ~2 minutes within the maintenance window provided. Updates will be posted to Trust if new information becomes available.

No incidents in the last 30 days

12:01 AM PDT - 5/28/2018
Published on: Saturday May 26th, 2018 - 12:01 AM PDT

No incidents in the last 30 days

Maintenance – Tableau Online UW2B environment

10:00 PM PDT - 5/26/2018 to 12:00 AM PDT - 5/27/2018
Published on: Thursday May 17th, 2018 - 3:30 AM PDT

On Saturday, May 27th, 2018 from 5:00am UTC to 7:00am UTC, the Tableau Online US-WEST-2B environment may be unavailable due to a third-party vendor’s need to perform maintenance to their infrastructure. During this time, users may be unable to access the US-WEST-2B environment for a period of up to ~5 minutes within the maintenance window provided. Updates will be posted to Trust if new information becomes available.

RESOLVED: Degraded | Tableau Online Dub01 - Users list not fully displayed

5:43 AM PDT - 5/21/2018 to 12:25 PM PDT - 5/21/2018
Published on: Monday May 21st, 2018 - 6:10 AM PDT

Update, 6:25pm UTC: Tableau Engineers have finished implementing a solution to the DUB01 environment and have brought this pod back into a healthy state. Functionality has been fully restored and we will be closely monitoring the environment. This issue is now being considered resolved.

-------------------------------

Update, 7:00pm UTC: Tableau Engineers are in the process of implementing a solution to display the complete list of users in the DUB01 environment. While no users have been removed, some sites in this environment may not be able to view a full list of all users in the site when navigation to the "Users" page.

Next update: 8:00pm UTC

-------------------------------

Update, 6:00pm UTC: Our team continues to investigate the best solution to restore functionality to the "Users" page in the DUB01 environment. Affected sites may not show the full list of users in the "Users" page at this time.

Next update: 7:00pm UTC

-------------------------------

Update, 5:00pm UTC: At this time, users in the DUB01 environment may be unable to view the complete list of users in the "Users" page. As managing user roles and licensing is unavailable for affected sites, we are upgrading this notice to a degradation. Engineers are working hard to bring this environment back into a healthy state.

Next update: 6:00pm UTC

-------------------------------

Update, 4:00pm UTC: Some customer sites have been restored and engineers are continuing to work to implement a full solution for all sites. Affected sites may not show the full list of users in the "Users" page at this time.

Next update: 5:00pm UTC

-------------------------------

Update, 2:30pm UTC: Tableau Engineers have identified the issue and are working to resolve the issue for all impacted users. We will continue to monitor the service until a full resolution has been confirmed. We apologize for any inconvenience this might cause.

Next update: 4:00pm UTC

-------------------------------

Update, 1:45pm UTC: Tableau Engineers are continuing to narrow down the root cause of users not appearing in the “Users” page. The team is engaged and working towards a resolution.

Next update: 2:30pm UTC

-------------------------------

Tableau Engineers are investigating an issue regarding users not appearing in the “Users” page.
This issue does not affect any functionality of Tableau Online and all users can logon and use the service as expected.

Next update: 1:45pm UTC

Maintenance – Tableau Online DUB01 environment

10:00 AM PDT - 5/20/2018 to 8:00 PM PDT - 5/20/2018
Published on: Saturday May 19th, 2018 - 8:20 PM PDT

On Sunday, May 20th, 2018 5:00pm UTC to Monday, May 21th, 2018 3:00am UTC, the Tableau Online DUB01 environment may be unavailable due to a third-party vendor’s need to perform maintenance to their infrastructure. During this time, users may have intermittent access to the environment within the maintenance window provided.