Service Pack 8
Release date: July 20, 2026
Service Pack availability
Service Pack 7 is available for the following release family:
- 2026.3: Release 2026.3.6
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-102129 | 68744 | Downloaded HTML exports displayed vertically stacked text and rendering artifacts for tables with hidden headers. | 2026.3.6 |
| INC-102318 | 69197 | Dashboards based on Spark SQL views could intermittently fail with lock errors during SQLx query execution. | 2026.3.6 |
| INC-101965 | 67887 | The Excel Add-in could fail to authenticate when multiple Incorta clusters were configured, preventing successful sign-in. | 2026.3.6 |
| INC-102258 | 69093 | When sorting a Summary table by selecting a column header, the sort was applied to an adjacent column instead of the selected column. | 2026.3.6 |
| INC-102532 | 69717 | Formula columns using the date() function might have become invalid during post-upgrade schema updates, resulting in dashboard errors. | 2026.3.6 |
| INC-102400 | 69327 | Joins involving duplicate parent-child table relationships were incorrectly marked as invalid in the UI. The invalid join warning message has been updated to indicate when the cause is a duplicate join, providing clearer guidance on the recommended fix. | 2026.3.6 |
| INC-102532 | 69717 | Some schema formula columns changed their data type unexpectedly, causing dashboards that relied on those columns to fail. Important: After upgrading to this patch release, load affected schemas from staging to restore the correct column data types and resolve dashboard failures. | 2026.3.6 |
| INC-101762 | 68117 | Users with the proper group permissions could not see dashboards in shared folders, even though other users with the same permissions could access them. | 2026.3.6 |
| INC-101888 | 68475 | Deleting a table in a schema that has an alias table referencing a previously deleted table in a different schema could leave the in-memory schema model in an inconsistent state, causing dashboards to fail with an IO error on subsequent queries. A service restart was required to recover. The fix ensures that the issue is handled without needing a restart. | 2026.3.6 |
| INC-101858 | 68254 | After restarting the Loader Service, the data agent stopped retrying the connection when it encountered a specific network error during reconnection, requiring a manual data agent restart to restore connectivity. The data agent now correctly retries on all connection errors. | 2026.3.6 |
| INC-101387 | Previously, the periodic metadata sync between the Analytics Service and Advanced SQLi could hang indefinitely when the metadata server was temporarily unreachable. The sync now retries automatically on connection failures, starting with a 1-minute wait and increasing up to 15 minutes, and recovers once the metadata server becomes available again. | 2026.3.6 |