Service Pack 11
Release date: August 19, 2026
Service Pack availability
Service Pack 11 is available for the following release family:
- 2026.3: Release 2026.3.8
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-102615 INC-102445 | 69922 68992 | The Join, Fuzzy Join, and Unpivot recipes could fail with a generic error: Could not get the schema, due to unhandled cases. The fix includes the following: ● Improved and descriptive error messages. ● Join and Fuzzy Join recipes: Data Studio now automatically renames columns that share the same name with different cases. ● Unpivot recipe: The Header Column Name and Value Column Name fields are now mandatory before saving the recipe. | 2026.3.8 |
| INC-102709 | 70112 | A schema could incorrectly show Finished With Errors status (with a blank error page) although everything actually completed successfully, while the non-mandatory COMPACTION step was still running at status check. | 2026.3.8 |
| INC-102688 | 70070 70313 | Selecting a link configured on a KPI title did not navigate to the destination URL. | 2026.3.8 |
| INC-103064 | Spark SQL views built on top of Analyzer views weren't invalidating their cache when the underlying schema was updated. | 2026.3.8 | |
| INC-102124 | 68802 | Opening and saving a measure formula in Insight edit mode could cause incorrect sorting when both the measure and dimension used formulas. | 2026.3.8 |
| INC-102069 | The public API returned an incorrect row count for insights with dynamic hierarchies. | 2026.3.8 | |
| INC-102810 | 70394 | Dashboards and folders on iPad Safari required a double tap to open instead of a single tap. | 2026.3.8 |
| INC-102667 | 70054 | Japanese text input in the rich text editor was committed at unintended times, preventing Japanese characters from being entered correctly. | 2026.3.8 |
| INC-100810 | The Insight Query endpoint returned a null value for the field parameter in case of formula columns. The endpoint now has a new optional boolean parameter, includeFormulaText, in the query request. When set to true, the formula expression is included in the response alongside the data values. | 2026.3.8 | |
| INC-102794 INC-103100 INC-102779 INC-102715 | 70013 70165 70310 70567 | A large number of concurrent short-lived connections could exhaust memory and cause SQLi to become unresponsive. The fix has improved connection handling and memory management under heavy loads and improved SQLi resilience in throttling mode by: ● Introducing a new CMC option, Max number of concurrent connections to SQLi, to limit the allowed concurrent connections to the SQLi service. Connections beyond the limit are rejected instead of queuing up. The default is 300; increasing this limit requires increasing the SQLi allocated memory. ● Decreasing the default Timeout to allocate memory before SQLi rejects connection to 10 seconds. | 2026.3.8 |
| INC-102804 | 70249 | Users could not download the Original View of an insight when Personalized View was enabled. | 2026.3.8 |
| INC-103028 INC-103306 | 70317 70954 | The drilldown indicator (white triangle on column headers) that shows which tabular columns have direct drilldown configured stopped appearing starting in 2026.3.5. | 2026.3.8 |
| INC-103157 | 70829 | Pivot and Aggregate tables with Merge Columns enabled threw an error: Cannot read properties of undefined (reading 'style'). | 2026.3.8 |
| INC-103187 | 70857 | The calculation of the expected time to execute a load job did not work correctly, causing the Load job taking longer than expected notification not to be sent when the Loader Service was down. | 2026.3.8 |
| INC-103052 | 70525 | Extra horizontal lines appeared on dashboards when row gridlines were enabled in tables. | 2026.3.8 |
| INC-102243 INC-103192 | 68999 70299 | Long-running queries in the Grouping and Aggregation phase were not interrupted after exceeding the configured timeout, causing subsequent dashboard requests to fail. | 2026.3.8 |