Service Pack 5
Release date: June 7, 2026
Service Pack availability
Service Pack 5 is available for the following release families:
- 2025.7: Release 2025.7.9
- 2026.3: Release 2026.3.3
Recommendation
It is strongly recommended to upgrade to the latest available service pack within your release family to ensure optimal stability, security, and continued support coverage.
Fixed issues
| Bug Identifier | Support Ticket | Description | Applicable Releases |
|---|---|---|---|
| INC-96799 | 61216 | Adding a new export folder entry in the CMC failed on the first attempt. | 2025.7.9 2026.3.3 |
| INC-100966 | 66627 | Exporting a folder failed when the folder or dashboard name contained a reserved character. The fix adds validation to reject names containing reserved characters (including, \, ?, *, :, ", <, and >) at creation or rename time when using methods other than the application UI. | 2025.7.9 2026.3.3 |
| INC-101377 | 67128 | The cleanup job deleted the join DDM version directory after it was created but before acquiring a lock, causing the active join calculations to fail. The fix ensures that the cleanup job preserves the most recent DDM version, regardless of its lock or database status, and skips any versions created after the cleanup job start time. | 2025.7.9 2026.3.3 |
| INC-101688 | 67861 | Applying a large IN-list filter on a dashboard insight returned incorrect and inconsistent result counts, including serial numbers not present in the filter list. | 2025.7.9 2026.3.3 |
| INC-100963 | 66319 | Insights referencing PostgreSQL views intermittently failed with a shared temp table population error, causing all subsequent renders using the same join to fail until the Analytics service was restarted. The fix ensures removing failed temp tables from the cache, allowing future executions to complete successfully. | 2026.3.3 |
| INC-101257 | 67082 | Dashboard queries against the same Spark SQL view were executed sequentially rather than in parallel, causing slow queries to block all subsequent insights. The fix ensures that multiple executions of the same Spark SQL view run concurrently without blocking. | 2026.3.3 |
| INC-91766 | The CMC previously allowed unlimited simultaneous logins per user. The fix introduces an internal configuration, cmc.maximum.concurrent.sessions that can be added to cmc.cfg, with a default setting of 10 sessions, to limit concurrent sessions per user. When exceeding this limit, the system automatically invalidates the oldest session. Restart the CMC after changing this setting. | 2026.3.3 | |
| INC-100192 | The BigQuery data destination was previously limited to authentication using an Incorta-managed service account. This fix introduces support for customer-managed service accounts, enabling compliance with InfoSec policies. | 2026.3.3 | |
| INC-100593 | Deleted schemas and business schemas in the Data Catalog continued to appear instead of being removed. | 2026.3.3 | |
| INC-101026 | In Data Quality rules, the Date Before and Date After conditions were not evaluated correctly, causing rows to be rejected. | 2026.3.3 | |
| INC-101245 | An error occurred while downloading insights as a PDF, preventing the file from being downloaded successfully. | 2026.3.3 | |
| INC-101390 | In Waterfall charts, multiple issues occurred: ● Smaller bars were difficult to distinguish when large subtotal values were present. A new Dynamic Visible Range option was added. ● Null break-by combinations appeared in charts. ● Visible break-by groups could disappear when hiding the first group. ● Date fields and subtotal titles could render with incorrect formatting. ● Subtotals could accumulate incorrectly across groups. | 2026.3.3 | |
| INC-101401 | The Kyuubi submit logs were mistakenly added to the Analytics logs. The fix ensures that these Kyuubi-related logs are added to advanced_sql.logs. | 2026.3.3 |