Update 5:00PM Pacific 6/29/17 (0:30am UTC 6/30/17)

This issue has been resolved, and access to REST API triggered extract refreshes is restored as of 4:59pm PT 6/29 (11:59pm UTC 6/30).

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

Update 11:30AM Pacific (6:30pm UTC) 6/27/17

Our engineers have identified a fix for this issue and testing is in progress. Next update will occur when the production release timing is known.

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

Tableau Online includes a feature to allow users to programmatically trigger an extract refresh via the server's REST API.

On Wednesday May 31, 2017, when this feature was enabled, a bug was introduced where extract refreshes may not be performed as expected.

Until this issue is resolved, we are disabling this feature where extract refreshes via the REST API will not be allowed.

We apologize for this inconvenience and thank you for your patience while our engineers work on a fix.

Update 5:00PM Pacific 6/29/17 (0:30am UTC 6/30/17)

This issue has been resolved, and access to REST API triggered extract refreshes is restored as of 4:59pm PT 6/29 (11:59pm UTC 6/30).

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

Update 11:30AM Pacific (6:30pm UTC) 6/27/17

Our engineers have identified a fix for this issue and testing is in progress. Next update will occur when the production release timing is known.

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

Tableau Online includes a feature to allow users to programmatically trigger an extract refresh via the server's REST API.

On Wednesday May 31, 2017, when this feature was enabled, a bug was introduced where extract refreshes may not be performed as expected.

Until this issue is resolved, we are disabling this feature where extract refreshes via the REST API will not be allowed.

We apologize for this inconvenience and thank you for your patience while our engineers work on a fix.

Update 5:00PM Pacific 6/29/17 (0:30am UTC 6/30/17)

This issue has been resolved, and access to REST API triggered extract refreshes is restored as of 4:59pm PT 6/29 (11:59pm UTC 6/30).

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

Update 11:30AM Pacific (6:30pm UTC) 6/27/17

Our engineers have identified a fix for this issue and testing is in progress. Next update will occur when the production release timing is known.

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

Tableau Online includes a feature to allow users to programmatically trigger an extract refresh via the server's REST API.

On Wednesday May 31, 2017, when this feature was enabled, a bug was introduced where extract refreshes may not be performed as expected.

Until this issue is resolved, we are disabling this feature where extract refreshes via the REST API will not be allowed.

We apologize for this inconvenience and thank you for your patience while our engineers work on a fix.

Update 5:00PM Pacific 6/29/17 (0:30am UTC 6/30/17)

This issue has been resolved, and access to REST API triggered extract refreshes is restored as of 4:59pm PT 6/29 (11:59pm UTC 6/30).

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

Update 11:30AM Pacific (6:30pm UTC) 6/27/17

Our engineers have identified a fix for this issue and testing is in progress. Next update will occur when the production release timing is known.

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

Tableau Online includes a feature to allow users to programmatically trigger an extract refresh via the server's REST API.

On Wednesday May 31, 2017, when this feature was enabled, a bug was introduced where extract refreshes may not be performed as expected.

Until this issue is resolved, we are disabling this feature where extract refreshes via the REST API will not be allowed.

We apologize for this inconvenience and thank you for your patience while our engineers work on a fix.

Update 06:12am 06/14: Our engineers resolved the issue by performing a modification on the way the Sync client was interacting with the Dub01 Online pod. The service appears now to be working as expected.
We do apologize for the inconvenience.

Customers might currently be experiencing issues to connect to Dub01 Online using the sync client also known as Tableau Bridge. Our engineers have been engaged and are actively investigating this issue in order to resolve it as quickly as possible.

Thank you for your patience and comprehension.

Next update at 06:15am PT

Update 06:12am 06/14: Our engineers resolved the issue by performing a modification on the way the Sync client was interacting with the Dub01 Online pod. The service appears now to be working as expected.
We do apologize for the inconvenience.

Customers might currently be experiencing issues to connect to Dub01 Online using the sync client also known as Tableau Bridge. Our engineers have been engaged and are actively investigating this issue in order to resolve it as quickly as possible.

Thank you for your patience and comprehension.

Next update at 06:15am PT