Skip to main content

Known Issues

AtScale contains the following known issues.

C2026.7.0​

Engine statistics require recollection after upgrade​

For upgrades to C2026.7.x from any version prior to C2026.6.x. After upgrading, engine statistics need to be recollected for all values. This is required to address a cache-integrity fix (see ATSCALE-44947 in the C2026.6.0 Resolved Issues). No manual action is needed. After the upgrade, the statistics will be collected as needed, by the system, based on system use.

On the first day of normal use, you can expect the following effects. These are transient and should resolve on their own.

  • Additional statistics queries (i.e. cardinality calculations, row counts) on your data warehouse. This may result in a small, one-time cost increase on consumption-billed platforms.
  • Model validation may temporarily not display validation errors (if present) until statistics are collected on the model. Model validation queries needing statistics will need to refresh to display. These refreshes are triggered when the user interacts with the model from Design Center. Reselecting and reentering the model later on after statistics are collected will display model validation errors, if present.

To mitigate potential effects of statistics upgrades, AtScale recommends you schedule the upgrade ahead of a lighter-usage period (for example, before a weekend) so repopulation happens under low load.

If you have any questions or concerns regarding upgrading AtScale and the impact of the statistics refresh on your environment, contact AtScale Technical Support through the https://help.atscale.com portal.

Issues with AtScale licenses that do not contain the data_catalog_api feature​

If your AtScale license does not contain the data_catalog_api feature, you may encounter the following issues:

  • You may receive the following error after successful catalog deployments: There is an issue with setting the default permissions to the models. Please go to "Deployed Catalogs" and set the permissions accordingly. This error is incorrect and can be ignored. You do not need to adjust your model permissions.
  • The Resource Permissions page for deployed catalogs may fail to load with an error of Error loading resource security groups. If you encounter this issue, contact AtScale Technical Support via the Help Center for assistance.
  • When using the AtScale add-on for Google Sheets, queries may fail with an error.

ATSCALE-50539

XIRR not currently supported on Amazon Redshift​

Note

XIRR is a Public Preview feature.

AtScale's XIRR UDF became inoperable from June 30, 2026 due to an AWS Redshift deprecation of Python language support for UDFs. AtScale has migrated to a Lambda UDF for C2026.9. If you require this XIRR Lambda UDF for an earlier version, reach out to AtScale Support.

Partition-based incremental aggregates can only be enabled at the global level​

Partition-based incremental aggregates are enabled/disabled via the aggregate.incrementalUpdate.partition.enabled setting. This setting is not currently supported at the model level. If you want to configure partition-based incremental aggregates, you should set aggregate.incrementalUpdate.partition.enabled at the global level.

ATSCALE-50738

PostgreSQL deployment update​

What you need to know​

AtScale utilizes PostgreSQL for its metadata store. When PostgreSQL is configured for high availability (with more than one replica), Bitnami’s PostgreSQL has a serious bug in its management of primary nodes, resulting in poor management and recovery services that can lead to duplicate primaries, platform instability and data loss. The result is that deploying AtScale with embedded PostgreSQL and a replica larger than one will likely create platform instability as Kubernetes auto-manages the cluster.

For environments that don’t require high availability​

AtScale will continue to ship Bitnami PostgreSQL with the default setting of replica=1. This configuration is effective and highly stable. It’s a solid configuration for POCs and non-production environments. Some customers may choose to run this configuration in production and utilize PostgreSQL’s backup options.

For environments that require high availability​

While AtScale has offered the embedded PostgreSQL for convenience, it is common for technologies that require a metastore, such as PostgreSQL, to leverage an externally managed database. AtScale recommends considering your SLAs when configuring production. If you require high availability, it is recommended that you configure AtScale with an external PostgreSQL (i.e., Amazon RDS) instance that can guarantee this SLA and ensure stability.

DEVOPS-7216

Enabling honeybee on PostgreSQL data warehouses causes engine instability​

Enabling honeybee on a PostgreSQL data warehouse after it has been connected to AtScale causes the engine to become unstable. To avoid this issue, AtScale recommends enabling honeybee on your PostgreSQL data warehouse before adding it in Design Center.

ATSCALE-28082

Is Aggregatable cannot be disabled on non-root levels in hierarchies with more than two levels​

In hierarchies with more than two levels, disabling the Is Aggregatable property on levels other than the root level is not supported. In future releases, models with such a configuration will not deploy to the engine.

ATSCALE-25328

Iris JDBC does not support CTEs​

The Iris JDBC driver does not support Common Table Expressions (CTEs), so the new feature that enables the query planner to use CTEs is not supported for Iris. If you are using AtScale on Iris, you need to set the following global setting:

query.planning.allowCtes: false

By default, this setting is set to true.

Identity Broker logout does not completely log out of Design Center​

Users who log in to the Identity Broker from Design Center, then log out of the Identity Broker, are not automatically logged out of Design Center. This is because the Identity Broker logout event interrupts the Design Center function.

ATSCALE-22180

Tableau: Double dashes in catalog names creates empty .tds files​

Double dashes (--) in the unique names of catalogs causes corruption of Tableau .tds file generation. This is because double dashes are reserved in many databases, and signal a comment in SQL. AtScale recommends avoiding this character pattern when creating and deploying catalogs.

ATSCALE-16605, ATSCALE-22167

Perspectives cannot contain multiple objects with the same display names​

Perspectives cannot contain references to multiple objects with the same display names/labels, as this results in errors at deploy time.

ATSCALE-22326