Known Issues

In some cases, when connecting to Tableau Server via mutual SSL, Tableau Desktop displayed an "error 6 SSL handshake failed" error message.

When using the NOW() function with a live connection to Snowflake, Tableau followed the data source location time instead of the time configured on the data source server.

When trying to create an extract of Sybase ASE using a MAX() or Top N extract filter, the extract would fail.

In some cases, valid calculations returned an "Invalid datetime error" error message.

In some cases, web authoring in Safari for iOS would fail to load with an error.

When attempting to open or web-edit a workbook connected to TabPy on Tableau Server, an "An unexpected error occurred. If you continue to receive this error please contact your Tableau Server Administrator" error sometimes occurred.

When running manual or scheduled Snowflake extract refreshes on Tableau Online and Tableau Server 2018.2, the refresh task fails with "Missing Password" error.

If the time zone on the host system is set to a time zone that is not identified as a named java time zone (Examples: -11:00, -12:00, -3 with 'adjust daylight savings automatically' disabled), TSM fails to initialize at step 13. These uncommonly used time zones in the Pacific makes java default to a generic value for the key Cfg.config.logging.time.zone_id.

In Tableau Server 2018.2, a DataServiceFailure error would occur when using published extracts if the operating system locale did not match one of the languages in which Tableau's UI is available.

When selecting Download Data in Chrome with the Grammarly extension installed, an  Uncaught TypeError: Cannot read property 'parse' of undefined error occurred.

In Tableau Online, when you tried to refresh a published extract which was hosted on AWS, sometimes the refresh failed with a "Lost connection to MySQL server during query" error.

Sometimes, refreshing an extract using Tableau Bridge consumed a large amount of RAM.

When attempting to view a workbook connected to published data sources, an ERROR: column ... is not available after aggregation error sometimes occurred.

For users with the Creator role, an Integrated Authentication option appeared when connecting to data which failed with a Access denied error

When viewing a story published to Tableau Online, Tableau Server 10.5.2, or Tableau Public using Safari on a Mac, text in the dashboard textboxes was being cut off with ellipses despite word wrap being set to On or Automatic.

When connecting to statistical files, if a field contained a NaN value in its first row, all values in that field would be recognized as NaN.

When using Thai language data, some fonts, including the default font, rendered some characters incorrectly.

In some cases, tooltips on a tree map had one character cut off.

Updated the Google Analytics connector with additional dimensions and metrics.

Appending a Microsoft Access file to an extract would fail with an error: Unable to append data from file. Microsoft JET database error 0x80004005: Unrecognized database format

After you performed a union of CSV or Excel files, merging mismatched fields would, in some cases, result in an Incompatible types error.

On macOS, if you exported a sheet as a crosstab and the file path or file name of the export contained a Chinese, Japanese, or Korean character, the export file would not be created or the resulting file name would have garbled characters.

In some cases, unexpected metadata queries would be sent to the underlying database in workbooks using an extracted data source.

Data appended to a .tde extract using Tableau 10.5 or higher could be lost when you edited the data source in an existing workbook.

Malformed SQL queries and resulting errors could sometimes occur when using a date parameter to modify a view.

A day to date relative date filter would only return data for midnight of the same day instead of the specified day to date.

In Tableau Desktop, when using the Append Data from File (or Append Data from Data Source) command to add data to an extract which had a data source filter applied to it, the correct “number of records added” notification appeaed, but the new data set did not appear in the view.

After setting the Start page to the Sites page, Server Administrators were unable to log into some Tableau Server sites from Tableau Desktop.

When using a date range slider in a dashboard in Tableau Desktop on a Mac, the values at both ends of the slider were partially hidden.

After upgrading to Tableau Desktop 10.5, blanks in shape files were no longer shown as NULL, which caused unexpected behavior in calculations.

Missing field errors could occur when opening workbooks connected to Google Analytics.

With accelerated graphics enabled, text that was formatted to use a large font size was not rendered correctly.

In some environments, the Edit Axis dialog would appear blank or as a black box.

In Tableau Desktop for Mac, it was not possible to connect to SAP HANA as the driver was not being properly recognized.

Using Tableau Desktop 2018.1, a debug.log file appeared when you installed or double clicked a workbook.

When you upgraded a workbook containing a live SAP HANA connection to 2018.1, a "No such column" error appeared when loading workbook.

When connecting to an Azure SQL Data Warehouse stored procedure with Tableau Desktop 2018.1, no values were returned.

“Tableau has stopped working” appeared when executing “addfiletoextract” after adding a calculation that contained a parameter.

Updated Japanese postcode data.

In histogram views, the axis labels did not match the bin values represented by the marks in the view.

When you were connected to IBM DB2 and using date filters, the TIMESTAMP_ISO function was sometimes used in queries which negatively impacted performance.

With accelerated graphics enabled, text in annotations that was set to a font size of 48pt or higher was not rendered cleanly on some systems.

In some Mac environments, visualizations would either disappear or turn into black boxes on when the Tableau Desktop window was dragged to a secondary display.

Updated postcode data for the Czech Republic.

An unknown collation error would occur when connecting to CSV files using the Norwegian Bokmål (Norway) locale.

In some cases where some sheets in a dashboard have been filtered down to display a single data point, tooltips containing views (Viz in tooltip) would show the same view when hovering over marks in different sheets.

In some cases, calculated fields containing multiple level of detail expressions returned unexpected results.

When using a relative date filter, the filter and Change list displayed the incorrect date range, although the data returned was correct and could be verified by examining the profile pane.

After editing a value in the Group and Replace editor and pressing Enter, the field scrolled back to the top of the value list.

Scroll bar was missing from the pivot pane.

When you connected to a Text file that was field separated by vertical bars, Tableau Prep did not always split the column as expected.

In some cases, Tableau Prep closed unexpectedly while trying to save a packaged flow.

In Tableau Prep 2018.2.1, it was not possible to change a field's data type from the input pane.

Values containing the character &, could not be renamed or edited.

When opening a .tfl file with custom SQL, Tableau Prep quit responding and the file did not load.

Unexpected characters appeared in parameter control buttons when viewing published views using Google Chrome set to display in Chinese, Japanese, or Korean.

When viewing published workbooks connected to Snowflake, the workbooks would intermittently fail to load with an error: Unable to connect to the data source. Try connecting again. If the problem persist, disconnect from the data source and contact the data source owner. Authentication token has expired. The user must authenticate again.

Fixed size dashboards that were wider, but shorter, than the browser window or mobile device screen could not be scrolled horizontally until the window was resized or you rotated the device.

Incremental extract refreshes for data sources containing a data source filter, and a join between tables with identical column names, could fail to refresh the data.

VizQL Server processes could sometimes crash when you loaded a view using URL filters/parameters.

Some REST API responses did not validate against the expected XSD schema.

In some cases, scheduled extract refreshes could not run due to Backgrounder processes being tied up with other internal tasks.

Some workbooks published to Tableau Server on Linux would constantly fail to load with an error: /tmp/.... is not an allowed path for query-file

When no Data Engine process was present on the Primary server, site export failed.

Data downloaded from a view using Download > Data showed internal names for any measures referenced in Measure Names on the view.

Saving a custom view would fail after sorting some views.

When opening a view that uses a published data source, an "Unable to connect to the data source DataServiceFailure" error sometimes occurred.

In some cases, duplicate site users were created for a single user during Active Directory sync.

When Tableau Server language was set to German, it was not possible to edit permissions.

In the Tableau Mobile app on Android devices, changing a filter selection or selecting a mark did not update the view or the selection would reset.

In some cases, if you had multiple sheets with viz in tooltip on a dashboard, the views in the tooltips would not render when you moved your cursor between the sheets.

SAP HANA variables and input parameters, set for a given workbook, were not respected when generating subscription emails for views in the workbook.

In some rare cases, changing a filter selection would cause an infinite spinner and the view would fail to update.

Downloading data from some workbooks containing special characters in the workbook or sheet titles would result in an internal error.

In Tableau Online, sometimes viz-in-tooltips failed to load.