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 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 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 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