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.

Presto and Athena drivers would not present an error when signing in with invalid credentials.

Error messages in the calculation field within Tableau Desktop would display in a different language from the chosen Tableau Prep language.

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.

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

Data Source details page will not load for users who have access to the data source but not to the project containing the data source.

It was not possible to reset verification methods in Tableau Online from the users TableauID profile (on Tableau.com).

A custom view would sometimes not reflect the dynamic parameter in a subscription email.

After publishing a workbook the dates along the axis line would sometimes change and become inaccurate

Set action made on source worksheet would not apply after publishing workbook to Tableau Online or Tableau Server when using published data source.

When viewing a visualization in Tableau Online or Tableau Server 2021.2 or higher that had a grey background it could be changed to white.

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.

When upgrading to version 2020.4 or newer, and the Server install has continually upgraded from 2018.1 or older while maintaining settings, it may not be possible to complete the upgrade. The upgrade failure message is “An error occurred during installation. Error occurred during encryption/decryption. Upgrade is unable to continue." Please see https://kb.tableau.com/articles/issue/error-an-error-occurred-during-installation-error-occurred-during-encryption-decryption-when-upgrading-tableau-server for solution steps.

The 'embed=y' parameter is not included by default in the URL generated by the "share" button in Tableau Server.

After publishing a workbook, a line could appear in a crosstab, which was not present in the rendering in Tableau Desktop.

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.

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

In versions up to, and including 2021.3, passwords longer than 240 characters are not supported in web authoring. Starting in 2021.4, this will be supported, however, the published recommendation to configure Tableau Server to use HTTPS, is highly recommended.

Re-designed metric card and list view on Tableau Mobile.

In this release, we are introducing support for Collections on Tableau Mobile. Collections are a new content type (that was released on Tableau Server & Tableau Online in 2021.2) which let you gather related items into an easy to access list.

Fixed a query compilation defect that led to reproducible crashes for a very small number of queries

Upgraded Unicode support from Unicode 9.0.0 to 13.0.0

When connected to a SAP HANA data source and connected to a synonym table, the variable values would not be applied in the Viz.

After upgrading from Tableau Desktop to 2020.2 or 2020.3 it could result in slower performance.

When editing joins, clicking "Create Join Calculaiton" could return an error message stating:
"Unable to complete action
Internal Error - An unexpected error occurred and the operation could not be completed.
Error Code: 6EA18A9E"

When loading a dashboard an error could occur and subsequently show the error message: "Resources exceeded during query execution: Not enough resources for query planning - too many subqueries or query is too complex."

A sheet in Tableau Desktop might not render properly when opened if the application window was too small and the document was opened by double-clicking the file.

An Unexpected Server error could occur stating, "TableauException: Internal error in file" where the file was the MultiDomain.cpp, when a hover activation of Change Set Values was performed.

After clicking on the "share" button on the toolbar, and then closing the dialog box, the user's next action would result in them being shown the Tableau Server login screen.

After upgrading to Tableau Server 2020.1, a large SAS extract refresh could fail with the error, "Exceeded per-process memory threshold." Large memory is consumed when this error occurs. KB: https://kb.tableau.com/articles/Issue/large-sas-file-extract-refresh-failed-and-huge-memory-consumption-observed-after-upgraded-tableau-server-to-2020-3-1.

After publishing a datasource with the overwrite option using tabcmd, the data source's schedule would be removed.

When guest access was enabled, some users were unable to open workbooks using the share link feature.

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

When using SSPI or Kerberos authentication in Tableau Server 2021.1, a blank screen appeared until the browser was refreshed.

When enabling external file store the command could fail and result in an error indicating that it had consumed all of the file handles available.

Tableau Server would always try to connect to OpenID Connect, even when using a forward proxy.

After publishing a viz to Tableau Server version 2021.1.2 the row and column banding might not render as expected.

A view would fail to render if the measure values were in the view, the data server and vizqlserver were on different nodes, and the user was prompted for credentials.

This would result in the following error message: "Field ‘Measure name’ in the datasource [sqlproxy.xxxxxxxxxxx].[:Measure Names] doesn’t exists in the database."

Some dashboard refresh jobs could be in a pending state for long hours and then fail.

In version 2021.2 guest users could receive a HTTP error 404, "page not found" error when accessing a shared URL.

Accounts that had a username which contained a space or special symbol could not change their password when the "Force Password Update" occurred.

Extract refreshes could fail with the error, "Process cannot access the file because it is being used by another process."