Known Issues in 2024 Releases
The following are the known issues in the 2024 cloud releases along with the workaround and fix version if any. This list may contain issues from earlier releases that haven't been resolved yet.
For the list of issues resolved in earlier releases, refer to Known Issues in 2023 Releases and Known Issues in 2022 Releases.
| Known issue | Status | Affected Versions | Workaround | Fix Version |
|---|---|---|---|---|
| Sending multiple schemas concurrently to the same target schema (dataset) in a Google BigQuery data destination may fail for the first time if the target schema (the BigQuery dataset) does not yet exist. | Open | 2024.1.0 | Do one of the following: ● Send (load) one schema first, and then send all other schemas. You can create a load plan with one schema in a group and all other schemas in another group. ● Create the dataset in the BigQuery project before sending the schemas concurrently. ● Execute the load plan again or manually load the failed schemas. | |
| When filtering the load jobs list by the In Queue status, single-group load plans that are in queue won’t appear on the list; however, they will appear when filtering by the In Progress status. | Open | 2023.7.0 and later | ||
| When enabling Spark-based extraction on a data source while running Spark 3.3, the extraction of the respective table fails. | Open | Spark 3.3 | Turn off the Enable Spark Based Extraction in the Table Data Source or Edit Dataset dialog. | |
| A formula column that only references a physical column with null values shows wrong results as the Loader Service does not respect the null values when materializing the formula column. | Open | 2022.12.0 and later | ||
The count and distinct functions return null values instead of zeros when using them in a flat table or a session variable. | Open | 2022.12.0 and later | ||
| When the Pause Scheduled Jobs option is enabled in the Cluster Management Console (CMC), the emails of manually activated scheduled jobs are not sent. | Open | 2022.9.0 and later | ||
| Scheduled jobs of overwritten dashboards and physical schemas are not deleted. | Open | 2022.9.0 and later | ||
| Access rights to a parent folder are not propagated to child folders and dashboards if the same access rights were revoked before. | Open | 2022.9.0 and later | ||
| Aggregated tables with hierarchical data do not support conditional formatting based on other measures when adding multiple attributes. | Open | 2022.9.0 and later | ||
Exporting a tenant with a global variable that uses the newly supported syntax (query or queryDistinct expressions) from a cluster that runs a release prior to 2022.5.1 and then importing it to a cluster that runs the same or a later release will cause the Edit Global Variable dialog to show an empty Value. | Open | 2022.4.0 - 2022.5.0 | You can manually edit the value to enter the query expression again or upgrade both of the source and target clusters to the 2020.5.1 release before exporting the tenant that you want. Note: This issue does not apply to exporting a tenant from a cluster that runs 2022.5.1 or a later release and then importing it to the same or another cluster that runs 2022.5.1 or later. | |
| No validation on functions is triggered in the Formula Builder when creating global variables. | Open | 2022.4.0 and later | ||
| Global Variables that return a list of values are not functioning properly when referenced in materialized views (MVs) or individual filters. | Open | 2022.4.0 and later | ||
Global Variables will not appear on the list of variables when referenced in a column individual filter, that is when you type $ in the Search Values box. | Open | 2022.4.0 and later | You can add the global variable manually, if applicable. In Query, Contains, and Starts With are examples of functions that accept a global variable as a filter value to be added manually. | |
Using the DISTINCT operator on a measure in a Pivot table that is built over an Incorta SQL View throws errors. | Open | 2022.4.0 and later | ||
| In an imported physical schema or tenant, the Disable Full Load option will be automatically enabled after changing the data source of an object to an Incorta SQL Table or vice versa, which will lead to skipping these updated objects in the next schema full load jobs. | Open | 2022.3.0 and later | You need to either disable the feature manually for objects that support disabling full loads (physical schema tables and MVs with incremental load enabled) or recreate the objects. Note: This issue does not apply to newly created Incorta SQL Tables. | |
| Incrementally loading a table without a key for the first time results in an error. | Open | 2022.3.0 and later | Attempt to load the table incrementally again | |
| Insights might not render when you run the same query multiple times for the same dashboard. | Open | 2022.3.0 and later | ||
| Email addresses added as CC or BCC in a scheduled data notification are not saved. | Open | 2021.4.3 and later | ||
| In the CMC under Nodes, the Restart button beside each Service does not function properly. | Open | Use the Cloud Admin Portal to restart the Services from the Configurations tab. |