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

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.

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

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

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

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

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.