"Flow execution error: Failure parsing AQL - LogicAssert itrColumns != inputQueryColumns.end()" could occur when running a flow.

CEILING() function could return incorrect results when using a scalar or a constant as the argument.

A system error would sometimes occur when running the sample flow.

The CEILING() function would sometimes return inconsistent results and also varied from Tableau Desktop.

When running a flow that contains a pivot step, an error would sometimes display, "Failure parsing AQL: No such column {[field]}."

The command line option to run a flow containing a TabPy script would sometimes display an error, "The Tableau Python (TabPy) server configuration is required. Enter a valid server configuration, then try again."

Published data sources would sometimes not be displayed in the Connections pane to search for data. The message would display, "Error: The server encountered an error. Try again."

A "collation mismatch" error could occur when running a flow with Microsoft Sql Server that contained a union and a join.

When using the command line option in 2020.3, Java warning messages could occur when publishing output.

It would not be possible to complete the Analytics Extensions Connection sign-in when the "Require SSL" checkbox was also marked and a valid SSL certificate was designated trying to access TabPy or RServe.

When the command line is used to run a flow, an "errorlevel" of 0 would return even if the command failed in some versions.

The user interface could become unresponsive when trying to copy and paste steps by "Ctrl+c" and "Ctrl+v".

On Macintosh OS, a CSV file with a Japanese file name could not be read.

When running a flow using an incremental refresh of Salesforce data, an error could occur stating "No such function ISNULL that takes arguments of type (datetime)."

A flow execution error could occur after joining an extract and an Excel file, "No such column [Item Name-1]."

The output step after a Left Only join could produce more rows than expected.

An error would sometimes display when a pivot is performed, "Query Text Limit of 67108864 Bytes Exceeded."

Beginning with 2020.3.3, any existing rich discrete value filtering in the users flow or a new flow created in grouped steps, the annotation would not show on the profile card as expected to see the change or to edit it. The work around is the use the changes pane on the left or from the flow pane in the top to access the rich discrete value filtering annotation/change they had made.