Known issues

When publishing or accessing a Tableau Online view that used the TableauServerUser variable with Tableau Bridge, a "Cannot evaluate user filter" or "Unable to connect to the server" error occurred.

An unknown license line item appeared in Manage Product Keys for Tableau Desktop which showed the license expiration date as "30-Dec-1899".

Published workbooks with a NOW() calculation would sometimes not display the correct "Site Time Zone for Extracts" setting.

When an alert is created on a MySQL data source, an error could result when using web authoring stating , "Unable to create alert because there was an error connecting to the data source."

When an additional data source is added using web edit, there is no prompt for credentials.

The text wrap does not display correctly including words being truncated and moved to the next line.

The fiscal year start month was reset after publishing to Tableau Online or Tableau Server 2021.1.

Page setup scaling options do not stay set when a workbook is download from Tableau Online 2021.1 via the user interface.

An intermittent error could occur refreshing an Amazon Redshift extract with the notification email stating, "Tableau Protocol Server process might be terminated, possibly due to system resource constrains or another external source."

Site admins were no longer receiving the extract refresh failure bell or email notifications when another user's data sources and workbooks fail to refresh.

When a workbook is published to Tableau Online or Tableau Server 2021.1+, a visualization using a custom number format on an axis would not display correctly.

An intermittent error could occur when accessing a visualization that is connected to a published data source, "No Tableau Server user found. DataServiceFailure."

Tableau Desktop and Tableau Prep were not displaying nested folders as destinations for publishing when permissions to parent project had been denied.

When multiple keys are activated on Tableau Server, registration data may not be available in the Tableau Customer Portal for all keys.

Starting in 2021.1+ , if SAML is configured, users were not getting the site selection option but redirected to a site.

Connecting to some Web Data Connectors from Tableau Desktop 2019.4 resulted in an error "The web data connector returned invalid data. Error Code: 95BE3012"

Workbooks using Oauth connections published with "prompt credentials" sometimes failed to publish with an "Internal Server Error TableauException" error.

While executing a query in Impala the error "The table .... does not exist" may occur when refreshing view or setting filters.

Worksheets containing a Boolean filter from a Snowflake data source change after publishing and show incorrect data.

Sometimes, temp files generated by Tableau Bridge continued to increase over time and were not cleared out as expected.

Tableau Online admin views sometimes took a long time to load, or eventually timed out.

When a scheduled extract refresh of a Quickbooks Online data source runs on Tableau Online, the following error occurs intermittently: "Intuit API Authentication error: Invalid authentication tokens. Login again and retry."

In Tableau Prep Builder, sometimes bigint data was rounded incorrectly.

String values with capital letters are treated inconsistently in out-of-sample values.

New option to Preview data based on refresh type (Full or Incremental) to accommodate new, potentially different, write options users can specify, is non-functional in Tableau Prep 2020.2.1.

In the new feature for 2020.3.1 called Write to Database, if the database or schema does not have any tables (it is empty), navigating to the schema or database will not be possible. The schema needs to have at least one table created to be visible for selection.

The Bridge client would sometimes crash when downloading a data source definition file from server.

"Error: Unable to complete action. Internal Error - An unexpected error occurred and the operation could not be completed. Error Code: 6EA18A9E" could occur when publishing or opening a workbook on Tableau Server when there is a table calculation, a parameter, and data blending in one worksheet.

When attempting to refresh or open a workbook with multiple data source, the error could display stating, "ERROR: no such field '[Calculation_XXXX:ok]', datasource='(name)."

An intermittent error: "Unable to complete action. Internal Error - An unexpected error occurred and the operation could not be completed. Error Code: 0E1EAFA4" could occur when editing a view.

A workbook could generate a "collation mismatch" error when trying to view full data with Excel and extract data sources.

OData V3 could fail to refresh using 2020.3+.

Presto data queries could fail with the error, "Value is not a number: java.lan.String", when converting custom SQL to decimal using the DECIMAL() function to cast the data type.

A "Driver not found" error message would sometimes result and the sign-button was unavailable when opening a workbook connected to an Impala data source.

Error Code: F5328B32, "Tableau cannot evaluate the query that results from this calculation" could result when more than one spatial calculated field is added to the view.

"Error code 2F0F5E42" could display when a workbook was connected to a live data source with joined tables.

Some users were not able to log into Tableau Online from Tableau Desktop when using a Gmail email account.

When opening and closing workbooks, aliases and sorts were sometimes not saved when connected live to Microsoft Access.

With PostgreSQL data, a timezone set by the initial SQL command when connected via JDBC would fail to apply.

The Impala data connector would fail to connect via the HTTP transport protocol.

An extract could repeatedly be created when switching between the sheet and the data source tab even after the extract had been created successfully.

Error code 6ea18a9e could display when performing an incremental refresh of an extract that uses custom SQL.

When generating the forecast for a Measure, an "Internal error" could occur.

In Tableau Reader, a workbook would fail to open when custom geocoding was contained.

An error would occur when changing the start page for all users, "An error occurred while changing your start page. Try again."

An automatic extract suspension policy could be applied to weekly or less frequent schedules in error.

When attempting to run a flow on a schedule with Tableau Server, the run would sometimes fail with the error, "System error: System error".

Adding a filter to a custom view using a query string did not work properly.

The install of Tableau Server could fail at step 12 of 35 when ".\" was used to designate the run as user.

The Elastic Server could fail to initialize after upgrading to 2020.4+ and running the" tsm security regenerate-internal-tokens" command.

An unrecoverable error can be thrown when web authoring a flow and switching to Field List View and then an output step is selected. Error displays, "Something went wrong and we couldn't complete the action."

In version 2021.2 of RMT, some topology changes without a Tableau Server restart were not being detected which could result in a lack of CPU information being reported for the process type that was added or removed.

The registration prompt would sometimes continue to prompt even when the registration was completed.

Using an Excel output file type could result in a malformatted error when re-selecting an earlier worksheet name with special character(s).

Excel output with an underscore in the file name could exchange the underscore with an exclamation point.

In version 2021.1.1, a performance issue could be experienced loading data in the Profile pane for a complex flow.

A prompt to specify a save location could prompt twice on a Macintosh operating system.

A rename transformation can be incorrectly applied to another field with the same name from a different data source when the connection is updated.

A downloaded workbook with multiple embedded extracts from published datasources could fail to refresh after republishing as a new workbook.

When using "Automatically detect settings" in the LAN settings menu, the Search for Data dialog window was blank when connecting to Tableau Server.

A reference line would show 0 for scientific values <= 1E-7.

A whole number would become a decimal number after converting to custom SQL in a Snowflake data connection.

With Tableau Desktop 2021.1, some visualization text would appear blurry on certain screen resolutions.

The ingestion pipeline could stall when the vizportal service was not ready which caused users the inability to view external assets after being granted view permission.

When trying to access a dashboard URL from a Kerberos SSO enabled Tableau Server, a user could be redirected to error code 43 and a login failed 401 response. This can occur when the Guest account is disabled at the site level but enabled at the global level.

After an upgrade to 2020.3, loading a view containing a published extract could fail to load with the error, "Could not find Hyper hosts to connect to. Unable to connect to the Tableau Data Extract server. Check that the server is running and that you have access privileges to the requested database."

The Site Administrator could modify a user's group membership even though Tableau Server was configured to only allow Server Administrators to manage users.

Dynamic data parameters would sometimes not work correctly when using a published data source and the message would state "Error: Value couldn't be assigned to this parameter."

Backgrounders could be in an unlicensed state due to using Prep and non-Prep cores.

After upgrading or installing 2020.4.X, the Data Server could fail to start or be unavailable.

Filtering from a URL query string would not respect the URL-encoded "+" sign.

"Subscription is suspended" emails were being sent to users despite the global subscription setting being disabled in TSM and the user setting selected to not receive the emails.

After upgrading a multi-node environment from 2020.3 and earlier and a core license is used, the addition of the Prep Flow Authoring and Flow Service could cause one of the nodes to be unlicensed.

The Edit Connection menu for a data source showed the Network Type as Tableau Online instead of Private network.

Some extract jobs were executed before the scheduled time.

When the Bridge client encountered a problem connecting to the Online server, there was a memory corruption issue.

We would launch a remote data source refresh job even when the given credentials failed to be saved.

Improved log messages to keep track of the DataServer session from start to finish.

Fixed the issue that caused the Windows credential store to sometimes not be filled correctly.

An error message could display on opening a workbook, "Error Code: ADE4BC90 Missing password. Unable to properly calculate the domain for the field 'Artifact Id'. Displayed data may be incorrect."

A WDC could cause Tableau Desktop to become unresponsive.

When a federated datasource is published from the Data tab by selecting "Create Data Extract" or "Activate Data Extract", the screens presented could be incorrect and confusing.

"Error Code: AE406838 [SQLSTATE:53100] Hyper was unable to grow the file partition" would sometimes occur when changing a filter in a worksheet. The Tableau Online error would show "[SQLSTATE:53S03] Cannot allocate bytes of memory."

Simba SQL Server ODBC driver version 1.5.5 required "Integrated Security=true" in the connection string for NTLM and Kerberos Windows authentication on Macintosh.

East Asian characters have the wrong orientation for rotated header labels and axis tick labels.

In version 2021.1, the background color of some tables changed causing the text to become unreadable.

A calculation error could display on Linux and Tableau Online stating, "The literal '##' is not a valid date."

The Extract Schedule Creation dialog could be missing when publishing a Bridge data source.

The Clean step in a Prep flow edit or create page only showed 50,000 records when more records existed.

Workbooks with an embedded PostgreSQL extract could result in a refresh error, "Deadline Exceeded".

The total header border would sometimes not display when publishing a workbook to 2021.1.

A database connection could stay open after a Prep flow had completed.

An intermittent error "AqlProcessor evaluation failed: [SQLSTATE:HY000]" could occur when refreshing a flow.

A dashboard filter could display incorrect results when the workbook language was different than the Tableau Online language set.

In Web Authoring, the authentication to Google Sheets was improved to no longer require authentication to each sheet.

It would be possible to experience a cache issue when writing back to the database updating the incorrect schema.

It would sometimes not be possible to connect to files on Box when using a forward proxy without authentication.

An incorrect export result could occur in a CSV file after replacing NULL with the ZN function.

The TSM CLI remote access did not prompt to trust the CA and the parameter '--trust-admin-controller-cert' was always required.

Tableau Prep flows would sometimes result in error containing "unexpected token: '['" when connected to a Salesforce data source.

In some cases, when customers attempted to change SMTP configuration options in the RMT UI, the UI would not reflect the changes on a page reload.

Date range filters in the Tableau Resource Monitoring Tool would accept, but not apply, invalid date range submissions. Better in-product guidance is provided for these scenarios.

The Tableau Resource Monitoring Tool UI includes notes on the number of connected Agents. The logic behind this has been updated to only reflect Agents that have been successfully registered.

Vizql sessions can be filtered by type in the Tableau Resource Monitoring Tool. A query issue was blocking this filter from properly displaying vizql sessions spawned by background processes when the 'Backgrounder Sessions' value was selected.

The Tableau Resource Monitoring Tool would allow more than one monitored environment to be created with the same environment identifier. This had the potential to cause some conflicts if multiple environments were actively being monitored with identical environment identifiers.

The Vizql Session Analysis report generated by the Tableau Resource Monitoring Tool included a broken blend that affected tooltips.

In some scenarios, the Tableau Resource Monitoring Tool would revert to leverage its self-signed certificate for https access to the web server. Communication would still be secure, but customer configured certificates would not be leveraged in version 2021.1 of RMT only.

When the Chrome or Edge browser was used to browse to RMT an error could occur stating "err_http2_inadequate_transport_security".