When an attempt to log in with Site SAML using Internet Explorer 11, login would fail with invalid username and password due to duplicate SAML assertions.

The parameter control date picker would display today's date as "Month YYYY" format which did not match Tableau Desktop.

When using the "#" character in a password and enforcing special characters was enabled with local authentication, an error would display that the password must include at least one special character.

Revision history on a site would be disabled when the Extract Encryption at Rest setting was changed via Tabcmd.

When an extract is created in the user interface of Tableau Server, the data source filters based on a date would be ignored.

Embedded views would sometimes fail loading the second visualization when multiple Sites were configured and there was no Guest user with "An unexpected error occurred on the server. Click the Refresh button in your web browser and try again."

A REST API call that specified a workbook name and contained special characters would fail.

A new Zookeeper instance would sometimes fail to start when deploying a coordination service if one already existed.

When recovering from a node 3 failure in a 3 node cluster, the "ServiceOperationTimeoutException" error was received after running the command "tsm topology deploy-coordination-service -n node1 --ignore-node-status node3". The command failed to redeploy the coordination service.

A dashboard containing a map would sometimes not load after applying a filter from all values to a single value.

The MIN() function added in the query causes performance degradation since 2020.2.0.

After successful login, an iframe embedded dashboard would fail to load if the URL contained the hash characters, "%23".

Group names created with 2 or more spaces in the name were incorrectly displayed on the Groups page.

On Windows Server 2012 R2 and Tableau Server 2020.3, degraded Viz load performance can occur when the New Relic Infrastructure Agent or other third-party monitoring software that uses WMI counters are running on the same node as Hyper and the Filestore.