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.
20 January 2026 - 1.123 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 | 20/01/2026 |
| Australia 01 | 22/01/2026 |
| United Kingdom 01 | 27/01/2026 |
| Switzerland 02 / Germany 02 | 29/01/2026 |
| Switzerland 01 | 01/02/2026 |
| Europe 01 | 04/02/2026 |
| Germany 01 | 08/02/2026 |
Attendant: Transfers and Consultation Calls for Outbound Sessions
Transfers and Consultation Calls are now possible for Outbound Call Sessions. This allows Nimbus users to engage with the customer first, then redirect them directly to an internal expert for further consultation. For the customer, this means minimized wait times with no further service calls required in order to get connected to the right expert.
🔎Added with this update:
- Attendant Console - Added support for scheduled and manual Outbound Calls & Call On Behalf, same as inbound sessions.
- Attendant - Safe Transfer to (internal or external) User / Phone Number / Nimbus Service
- Attendant - Blind Transfer to (internal or external) User / Phone Number / Nimbus Service
- Attendant - Consultation Call (internal or external) User / Phone Number. Nimbus Services are not yet supported.
- 💡Updated reporting behavior for these actions: In a multi-service scenario, where the first service handles the outbound task, and then transfers to another service, the task direction on the receiving service will be set to inbound.
Data Privacy Settings: Caller Anonymization
Caller Anonymization helps organizations to reduce exposure of personally identifiable information, supporting stricter privacy and compliance requirements. It limits what frontline users see, without blocking the workflow needed to help the caller. This lowers data‑handling risk while keeping service quality high.
Added to Nimbus:
- Caller Anonymization - new configuration item in the Administration. Used to centrally 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).
- Default disabled for all services. Once enabled, either all incoming PSTN calls OR the list of defined “Caller Anonymization” regular expressions will be applied.
☝Please note:
- This feature will be activated only on customer request. Once activated and configured, anonymized entries cannot be restored.
- Anonymization is not retroactive, and only applies to call sessions as long as the feature is enabled.
- Anonymization scope and feature limitations apply. For more details, refer to the Data Privacy Service Settings > Known Limitations.
Other Changes and Improvements
- Instant Messaging / Workflow Activities / WhatsApp Integration in Twilio: Added support for the “Web Request” activity when handling Instant Messages via workflow using the Twilio WhatsApp integration.
- Assistant - UI size was increased slightly. To accommodate new Consultation Call UI elements, Assistant will increase size temporarily, but return to the new standard height afterwards.