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.  Request is to support impersonation with Tableau Bridge.

When publishing a data source from Tableau Desktop version 2022.2 or higher to a lower version of Tableau Server such as 2022.1, an error would occur stating, "An error occurred when publishing the data source. Cannot publish to Tableau Server.  Please make sure you are connected to a compatible version of the server." For more information please see this Tableau Knowledge Base article.

Row and column divider borders are thicker in the header than in the pane starting with version 2021.1.

NULL values would remain in the Quick Filter when only NULL values are excluded in a dimension filter starting with 2022.2.0.

Queries of a virtual connection could be unsuccessful when included columns are renamed or removed from a database. The workaround is to edit the virtual connection and replace or delete these columns, and then republish the virtual connection.

Workbook utilizing a polygon map or territorial mapping has a hole or gap when published to Tableau Cloud or when opened in the latest version of Tableau Desktop.

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.

Scheduled extract refreshes could be intermittently skipped.

In a project description when parenthesis are preceded by an upper case letter, the parenthesis and text within the parenthesis would not be displayed in the project tooltip.

On the Explore page list view for data sources, the last modified date could display an incorrect value. The data source details page does have the correct last modified date.

When refreshing or connecting to Amazon Redshift in Tableau Online, errors would sometimes display showing "Error occurred while trying to prepare a query" or "[SQLState XX000] extraneous data in \"T\" message." Amazon Redshift driver updated to 1.4.53.

Okta SCIM could reset a user to a Viewer role when the name changed in Okta even when the site role was not configured to map to Tableau Online from Okta.

The sort order of a calculated field could be changed or duplicated after replacing the published data source using the REST API.

Selecting one item in a row or cell can sometimes cause the entire row to be selected. If selecting other marks on a crosstab in a quick succession, a crash could occur.

Scheduled data alerts are not automatically triggered when data is not scheduled to refresh.

When attempting to refresh a Google Analytics data source in Tableau Cloud, the refresh is sent to Tableau Bridge instead of connecting directly from Tableau Cloud.

Virtual Connection updates are not reflected in related Data Sources.

When loading a dashboard that contains a web object to a web page that has a text box, the cursor goes to the text box and the user is sent to the bottom of the dashboard on load instead of staying at the top of the dashboard causing the need to scroll up.

It is not possible to export a specific sheet using the JavaScript showExportDataDialog function starting with version 2022.1. For more information see this Tableau Knowledge Base article.

It is not possible to create an extract for a Google BigQuery virtual connection.

It is not possible to connect to a Presto DB server that is using SSL with Tableau Cloud but Tableau Desktop can connect. The error received in Tableau Cloud is "[Simba][Presto] (1020)...Peer certificate cannot be authenticated with given CA certificates."

Quickbooks Online extracts could fail to refresh with error, "No realm ID is detected", when using saved credentials for the data connection starting with Tableau Server 2022.3 and on Tableau Cloud. For more information see the Tableau Knowledge Base article.

Marketo extract refreshes fail in Tableau Cloud with the error, "Unknown failure (status code=1003)". Refreshes are successful with Tableau Desktop.

Saml-enabled Tableau Cloud users may be unable to login because the password field displays instead of being redirected to the IdP. For more information, please see this Tableau Knowledge Base article.

When provisioning an Azure AD user that was initially set as "unlicensed", the user could become a "Viewer" after a sync job was run with Tableau Cloud.

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.

When a user had a Google Drive enabled for their Tableau Prep Repository folder, they would not be unable to delete "Recovered Flows" from the Prep Builder UI. The workaround is to turn off Google Drive sync and manually delete the folders in the My Tableau Prep Repository/Recovered Flows directory.

The list of tables when connected to a PostgreSQL database would not show all the tables if there were more than 16384 tables.

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

Taking a backup while using the --multithreaded flag would cause a file handle leak on Windows resulting in high cpu usage for the WMI process.

No error would display when resetting a password and the new password violated the password policy set. This behavior began in 2021.2 and the user could not log in after resetting the password incorrectly.

The browser Options menu would not display when performing a right-click in the filter search box on Tableau Server 2021.2 and newer.

Changing the input parameters of a SAP HANA data source and republishing the change to Tableau Server does not show the changes when opening a workbook from Tableau Server that connects to this updated data source.

Running "tabcmd refreshextracts" with the "-addcalculations" flag caused the error, "SQLSTATE:58S01" and "Hyper was unable to resolve the database file path". This error occurred in versions 2021.2 and higher, but does not occur in 2020.4 or 2021.1.

It would not be possible to search users or groups on the permission for content edit screen where the username or group include some Japanese characters (dakuten, handankuten).

When using the ATR activation method on Linux, it is possible for the activation server to crash and Tableau Server to become unlicensed.

When upgrading from 2020.3 or 2020.4 to a higher major version, the upgrade could fail due to Ask Data being unable to start up during the rebuild index stage of the upgrade.

With the ATR activation method, Server can become unlicensed when the product keys do not all have the same expiration end date and one key has expired.

Error code 305B73A6 can occur when dragging and dropping a dimension and using a BigQuery Virtual Connection.

A published data source could show the wrong data in Ask Data and Web Authoring due to the data sources having the same name but differing in case.

Tableau Server on Linux can become unexpectedly unlicensed when not using the ATR activation method.  More information is available in this Tableau Knowledge Base article.

A Vizql service crash would occur when opening a workbook with an MSAS OLAP cube data source using driver version 15 or 16 in Tableau Server starting in 2022.1. Further information is available in this Knowledge Base article.

When Tableau Server is activated via the ATR activation service, LBLM licensing on Tableau Desktop and Tableau Prep could fail with "No seat capacity found for Login-based License Management" with versions 2021.2.15 and newer, and 2021.3.13 and newer, but not 2021.4 or 2022.1.

In External Actions, after choosing "Add a constant" in the map fields dialog, it is not possible to switch to another option.

In External Actions, if a dashboard is published with a configuration error in the extension, in View mode, there will be no error and the button will never become enabled.

External Actions cannot execute a flow with a Collection Variable input of type Currency.

It would not be possible to apply node roles to the topology as a "500 - Server Error" would occur in versions 2021.3 and 2021.4, but no error would occur in higher versions.

When configured with the ATR activation service, Tableau Server HA does not have a grace period if the initial node goes down.

Starting with 2022.3, when Guest access is enabled on a Tableau Server with Core licensing, the Data Orientation pane is available for embedded users, including the Guest user. For more information, please view this Tableau Knowledge Base article.

Starting with version 2022.3, the TSM UI shows a new service, the "Connection Pooling Service", which is not configurable or functionally available yet. Please see this Tableau Knowledge Base article for more information.

Tableau Server is incompatible with Windows Server 2022. For more information, see this Tableau Knowledge Base article.

After an upgrade to Tableau Server 2022.1.7 or later, a high sustained CPU usage caused by Hyper may result in Tableau Server becoming inaccessible. Please see this Tableau Knowledge article for more information on versions affected.

When uninstalling the Resource Monitoring Tool agent on Windows, the setup process would fail with the error: "One or more issues caused the setup to fail. Please fix the issues and then retry setup." More information is available in this Tableau Knowledge Base article.

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.

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

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.

Running a flow with a New Row Step on a Field with Type Conversion while using a published data source as an input, the flow would sometimes fail.

Bridge errors could occur when Bridge is performing an extract refresh while not logged in.

Invalid tokens cause Bridge remote refresh jobs to stall.

In version 2022.3.0 and 2022.4.0, the "Hide card" option could be missing on the context menu of sets, legends, highlighters, and parameters.

The custom format of a decimal number on an axis could change after being published to Tableau Cloud or Tableau Server.

The OneDrive and SharePoint Online connector could have data missing from the site listing result.

Publishing data roles to projects with locked permissions would sometimes result in an error.

When renaming a field with the toolbar set to "Show List VIew", the entire field would be removed from the flow if the delete key was used in editing the name.

Prep would sometimes not read Oracle Data Source Names from ODBC Data Source Administrator.

When attempting to run a flow in Online, the following error would sometimes occur, "[SQLSTATE:53S01] The query exceeded the CPU usage limit of 5500 seconds"

Prep Builder could crash when removing a connection.

A Tableau Prep flow could fail to refresh the access token on Tableau Server using Snowflake OAuth with Private Link.

A warning could occur stating, "One or more input files aren't in your organization's safe list" when publishing a flow or configuring "*" to allow all paths for input.

Japanese characters (half and full-width Hiragana and Katakana) could not be distinguished after published to Tableau Server.

Addressed issues with internal Tableau Server APIs.

When building a cluster and adding nodes into the initial node, the recognized CPU core number did not match the real machine specification.

Content Exploration service would not fail over in a HA configured Tableau Server. Web client can authenticate and navigate to Tableau Server, but content view, explore, create, etc fails, with multiple "An unexpected error occurred."

When importing a specific user and the user is successfully added but is not showing on the user list, an error will display when trying to add the user again. For more information, see this Tableau Knowledge article.

After scrolling down in a view then selecting a filter, the scroll bar moves back up to the top.

A parameter control list box could be open and stuck in a specific location in a browser window. This behavior only occurs when you double-click the parameter selection box before the entire dashboard is rendered.

After upgrading, or after restoring a backup to a new install to Tableau Server 2022.3.0 and there is a large user base, the server may be slow or inaccessible, with users unable to log in. For more information, please see this Tableau Knowledge Base article.

When filtering a dimension on a worksheet, then changing the dimension via a parameter, other worksheet(s) could disappear.

Dynamic parameters would not load the DATETRUNC value when a workbook opened using an embedded data source.

Workbook performance could be slower when using Virtual Connections.

The maestro.output.write_to_mssql_using_runas TSM command has been introduced to allow write access to a Microsoft SQL Server database using Run As credentials.

Accessing content in a site or server that you're not currently signed in to is now easier with an improved flow.

The Ask Data dashboard object was disabled when extensions were disabled.

DUO MFA could block older versions of chrome and cause a failure in the initial login attempt with a WDC connection.

A warning could occur when publishing a flow to Tableau Server stating, "One or more input files aren't in your organization's safe list" even when all paths are configured for input.

The command "tsm maintenance cleanup" can make the Apache error.log file inaccessible to other processes on the Windows OS.

The Data Engine folder was filling up quickly and backups could fail.

Published data sources that are connected to web data sources could take a long time to refresh.

When changing a published data source from a live connection to an extract, the following error could display "LogicException: Internal Error - an unexpected error occurred and the operation could not be completed."

The values in a multi-select dropdown list could be missing values if the sheet names contain a percent (%) sign.

ContentExploration and Interactive service could constitute up to 50% of logs on an inactive server.

A fiscal year showing on a continuous axis in Tableau Desktop would not display correctly in the published version.

Publishing a data source with the REST API then downloading the TDS file could be missing the metadata-record connection information compared to publishing a data source from Tableau Desktop.

When attempting to change a date filter, the following errors could occur, "Unable to complete action month out of range. Value '-2' must be between 1 and 12. Error Code: 58D44822." Another error that can display is "TableauException: month out of range".

When attempting to login to Tableau Cloud from Tableau Desktop "ALT-GR" can not be used to input symbols on non-English keyboards.

After selecting "open workbook" from Tableau Desktop not all published workbooks would display.

The "Publishing" dialogue box name dropdown would sometimes display workbook names.

Loading embedded dashboards with Extensions when using connected apps would result in an error for the extension.

A Flow error could error when loading a data source which contains a backslash in a column name. Any non-US Superstore sample files will produce an error such as "Error renaming field [Country\Region] to [Country/Region]. Unknown field name 'Country\\Region'."

The "download" option would sometimes be missing from the "Actions by All users" admin view.

Tooltips or filters would not respond when embedded into the Salesforce Lightning Web Component unless running in full-screen mode.

The parameter body text font color would be displayed incorrectly.

When removing a project the dialogue to confirm is truncated in Japanese.

ASCII code would show instead of Chinese characters in the "shared with me" dialogue.

An error would display, "Error parsing command parameter value string", when clicking Reset Name for all fields in web authoring. The field names do reset but the error message displays.

It would sometimes not be possible to acquire a JDBC Connection for the TDS Service.

For External Actions when a string is mapped to a boolean flow input, any non-"false" string defaults to "true".

An error would sometimes occur when moving a workbook to another project resulting in the following error message, "Tried to send an out-of-range integer as a 2-byte value: 33492".

When using Tableau Webhooks an error may occur stating "Webhook FAILED: [HTTP 408] Unable to connect to the url https://webhook..." when there is a proxy server.

Some backgrounder tasks showed a task type of "Unknown" despite being recognized.

In some cases, VizQL session lengths would be inflated.

Tableau Processes chart aggregation would not reflect resource consumption in line with the overall Performance chart.

Background task run times were sometimes miscalculated.

Large queries would sometimes erroneously report 0-second durations.

Data Query usernames were sometimes marked "unknown" even though the associated VizQL session had a known username

Generating a chargeback report would cause the subsequent attempt to download the logs bundle to fail

OneDrive and SharePoint Online extracts could fail being refreshed in Tableau Cloud.

Workbooks and data sources using the OneDrive and SharePoint Online connector have unexpected publishing options.

Prep Flows can intermittently fail with large data sources or complicated flows and result in the error, "System error: TableauException: Service Unavailable. Check to make sure the service is running."

When loading a view with a workbook that has a live connection to a published GBQ data source it would sometimes result in the following error, "LayeredProtocol: Missing attribute error".

When using a URL action to load another dashboard and specify a field value containing an ampersand character, the URL is rewritten and fails to load.