This page will always reflect the latest Release Notes, recent improvements and changes made to Nimbus.
Other Information Resources:
- Our Release Note History contains information on all previous releases from this year.
- Updates on our Nimbus Power BI Template are distributed on request. Please refer to the Nimbus BI Template Release Notes for updates.
- Also visit the following sources to stay up-to-date on Nimbus in both features and (upcoming) maintenance:
INC External News Resources
📣Important Announcements
Please take note of the following long-term and ongoing announcements below:
INC OData Server-driven pagination
OData Server-driven pagination
Starting February 2026 the Nimbus OData API handles large dataset requests with pagination using @odata.nextLink. Paginated results with a maximum of 10'000 entities per response are enforced.
Impacts to customers may not be obvious (non breaking change), but if the interface consuming the OData is not ready to handle pagination, partial results may be “silently" shown.
✅Actions required:
-
If you are using the Nimbus Power BI Template version 1.122 or above, you can expect it to handle
@odata.nextLinkout of box.
→ Unless your template has been modified, there is no need to take action. In principle, older templates should also handle this automatically, however in case of problems, we recommend to always check if you can reproduce the issue with the most recent template listed in the Nimbus BI Template Release Notes. - When using custom solutions to consume OData you must familiarize yourself with the specifics of the tools and interfaces you use to ingest data from our OData API.
🤔What is @odata.nextLink?
🔎@Odata.nextLink is…:
- … a property used in OData responses to support pagination. Its presence indicates that the response is larger than what can be fit in a single response.
- … an indication that there are more results to be fetched, before the request is fully satisfied.
- … URL that can be used to call and retrieve the next page of results. The URL is server-generated (never modify it).
- … an OData standard. Typically returned by OData services including Nimbus, Microsoft Graph, and any OData v4-compliant API.
- … essential for consuming large datasets.
- … handled out of the box by most mainstream data platforms that claim native OData ingestion support and have native OData connectors (e.g. Power BI, Excel, Azure Data Factory, etc.).
🔎Things to be aware of:
- A system that sources data from the OData relying on a non-paged behavior may quietly end up with partial query results.
- Systems that rely on custom logic to extract OData may not handle pagination automatically and may need manual intervention to handle it. E.g.:
- Raw HTTP clients (curl, Postman, custom scripts)
- Generic REST connectors without OData awareness
- Older OData v2-only connectors (some legacy tools)
- 10,000 is the maximum set – not a guarantee. Some pages may contain fewer records.
🔎 @odata.nextLink works as follows:
- The data client generates a request to the OData service.
- The OData service responds.
- The presence of
@odata.nextLinkin the response indicates that the server has more data available. - Clients must continue issuing requests using the provided URL until no
@odata.nextLinkis returned.
🤔How does it work in the BI Template?
💡Good to know: The default official Nimbus Power BI Template does not need to be updated in order to handle the introduction of "@OData.nextLink". Power BI expects this behavior and handles it automatically.
☝If you customized the template, ensure that you are familiar with your code and how this could interfere with the standard @Odata.nextLink behavior. If unsure, update the default template to the newest version.
🔎How does Odata.nextLink improve stability of the OData service with Power BI?
| ✅ With server paging Power BI | ❌ Without server paging Power BI |
|---|---|
|
|
🤔Which Nimbus data is affected?
Impacted OData entities from the Nimbus Reporting Model and Data Aggregation are as follows:
ServiceSessionsAggregatesUserSessionsAggregatesUserStatesAggregatesServiceSessionsUserSessionsUnifiedSessionsTransferSessionsCallers
End of announcements. Regular release notes continue below.
11 February 2026 - 1.124 Release Notes
🔖 This is a major update, bringing many new changes and improvements into Nimbus. This update is rolled out sequentially on our clusters:
| Cluster | Update on |
|---|---|
| United States 01 | 11/02/2026 |
| Australia 01 | 12/02/2026 |
| United Kingdom 01 | 17/02/2026 |
| Switzerland 02 / Germany 02 | 19/02/2026 |
| Switzerland 01 | 22/02/2026 |
| Europe 01 | 25/02/2026 |
| Germany 01 | 01/03/2026 |
OData Query: Enforced Pagination
We made improvements to the existing Nimbus OData Feed queries to enforce paginated results. This limits the number of records in the response, ensuring to avoid timeouts, API constraints and other errors related to large and parallel data set queries.
🔎Added with this update:
- Limited the number of records in the OData feed response to 10000 per page.
- The OData query supports clients to page through the result set without having to dynamically adapting the OData filter.
✅Checking pagination readiness:
- When using the Nimbus Power BI Template version 1.122 or above, you can expect
@odata.nextLinkto work out of box with no further action required.
🔎 Download links can be found on top of the BI Template page itself. - When you are accessing the 3rd-party solutions, please visit our OData Feed page and read the chapter on “Result pagination”. On most modern OData clients,
@odata.nextLinkpagination works without any additional actions required.
Data Privacy Settings: Caller Anonymization
💡This feature was added with the last release and enabled only on customer request. With this release, it is available to all Nimbus customers.
Caller Anonymization is a new feature added to Nimbus which helps organizations to reduce exposure of personally identifiable information, supporting stricter privacy and compliance requirements.
Added to Nimbus:
- Caller Anonymization - new configuration item in the Service Administration. In the configuration item, you can define how incoming PSTN numbers are identified for anonymization (e.g. opt-in numbers by specific region) by using regular expressions.
-
Data Privacy Service Settings tab added. Allows to steer the "Caller Anonymization" feature per service (default: disabled).
- When enabled, Caller Anonymization will mark Customer identifying fields in the Nimbus UI as “Anonymized on request”.
- KB Update: Updated System Fields and Parameters tables with a new “Caller Anonymization” columns and a separate chapter at the bottom to highlight the scope of this feature.
🔎Learn more about the scope of Caller Anonymization
INC Caller Anonymization Scope
| Type of Data in Scope | Field Names affected by Caller Anonymization (System Fields and Parameters) |
Content DURING live session (My Sessions / Attendant Console / Assistant) |
Content AFTER session in short-term storage (Sessions List / My Sessions) |
Content in LONG-TERM storage (Nimbus Reporting) |
|---|---|---|---|---|
|
Nimbus |
|
Shown (required to support operational handling (e.g. Power Automate) |
Shown as “Not Available” | N/A - Not stored |
|
Shown as “Not Available” because Customer Identifier is “Anonymized on Request”
|
Shown as “Not Available” | N/A - Not stored | |
|
Shown as “Anonymized on Request” | Shown as “Anonymized on Request” | N/A - Not stored | |
|
|
Shown as “Anonymized on Request” | Shown as “Anonymized on Request” | Shown as “Anonymized on Request” | |
|
Nimbus |
|
Shown as “Anonymized on Request”
|
Shown as “Anonymized on Request” | Shown as “Anonymized on Request” |
|
N/A | N/A |
Is set to true when Caller Anonymization is enabled. |
|
|
Nimbus (Custom Context) Parameters Nimbus |
☝Custom Data and Address Books are NOT in scope of Caller AnonymizationThe following data might still be visible during a call and needs to be handled accordingly:
✅Related action: Extension Service Settings
|
|||
☝Before enabling this feature
- "Caller Anonymization" Data Privacy Service Settings > is default disabled for all services. Once enabled, either all incoming PSTN calls OR the list of defined Caller Anonymization regular expression configuration items will be applied. → As data gets permanently as “Anonymized on Request”, please read the feature page carefully to understand the effects and follow-up actions required when using this.
- For more details, refer to the Data Privacy Service Settings > Known Limitations / Anonymization Scope chapters.
🔎Notes for this release
- Caller Anonymization is not retroactive, and only applies to call sessions as long as the feature is enabled.
- When enabled for the first service being called, anonymization will persist through transfers.
- Anonymization scope and feature limitations apply.
- This is the initial release version: Only Audio/Video modalities for inbound and outbound tasks are supported.
- No support for Transcription or Virtual Users, as involved AI agents use personal identifiers in their parsed call data.
Other Changes and Improvements
- Custom Roles - improvements to tooltips to be in-line with updates to our User Role (RBAC) Matrix and the detail CRUD permissions.
