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.
- To stay up to date on Nimbus feature and upcoming maintenance, please visit the following resources:
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. - In case you need to refresh and view large sets of data regularly, we recommend looking into setting up Incremental Refresh using Power BI Online services. This will automate and schedule the refresh procedures, decreasing the amount of data loaded for each ongoing time increment.
- When using custom or 3rd-party 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
🤔Why does the data refresh take longer after this change?
🔎There are two reasons to this:
- Equal load distribution: OData pagination is a change that we have implemented to improve stability of the architecture, serving concurrent requests from multiple tenants simultaneously. This is to ensure a fair and equal load distribution of available server resources amongst all Nimbus customers.
- Consistent performance: Compared to the previous setup, OData pagination could in some cases make the refresh times appear inconsistent, even on an seemingly identical data scope. The reason – particularly with very large datasets – was that multiple sequential requests to retrieve all data were required.
💡For these reason we recommend to implement Incremental Refresh and be mindful of the size of the query when hitting the OData Feed.
End of announcements. Regular release notes continue below.
04 March 2026 - 1.125 Release Notes
🔖 This is a major update, bringing many new changes and improvements into Nimbus. This update is being rolled out sequentially on our clusters:
| Cluster | Update on |
|---|---|
| United States 01 | 04/03/2026 |
| Australia 01 | 05/03/2026 |
| United Kingdom 01 | 10/03/2026 |
| Switzerland 02 / Germany 02 | 12/03/2026 |
| Switzerland 01 | 15/03/2026 |
| Europe 01 | 18/03/2026 |
| Germany 01 | 22/03/2026 |
Inbound SMS and WhatsApp support via Twilio: General Availability
Nimbus omnichannel capabilities are expanded with SMS and WhatsApp. The Twilio integration will be available across all clusters as of the planned deployment date.
With this feature, WhatsApp and SMS communication channels are added under Instant Messaging modality, allowing seamless management within the existing Nimbus workflows. Incoming messages can be distributed to Nimbus users, ensuring fast and efficient responses. Combined with Nimbus’ ability to handle tasks in parallel, this integration offers an additional and highly effective way to engage with customers. Moreover, your customers can easily reach you in their preferred channels bringing customer experience on the new level.
🔎 Added to Nimbus with this release:
- Modalities Service Settings updated with WhatsApp/Twilio settings and respective workflows.
- Added Instant Messaging WhatsApp / SMS support for all Workflow Activities.
- Updated Messaging Entries and Provider Connectors for SMS usage.
- Nimbus API > GET Service Details method now retrieves SMS / WhatsApp integration details as well.
- Updated Use Case - Setting Up Instant Messaging for showcasing the various integration paths and leading into the specific topics:
 (Nimbus light theme example) |
 (Nimbus dark theme example) |
Direct Call Reporting: Tracking Direct Calls made to MS Teams
INC Preview Feature
This feature is in PREVIEW and may not yet be available to all customers. Functionality, scope and design may change considerably.
💡This feature is already in preview and will be made available for general use in a following release.
Previously, when Nimbus users accept a direct call via MS Teams, they are not available for handling tasks from Nimbus services. While direct calls enable immediate, private, person-to-person conversations, they don't appear in daily reporting, causing gaps in performance tracking. The Direct Call Reporting feature addresses this scenario, closing the gap between reporting Nimbus calls and direct calls.
🔎 Added to Nimbus with this release:
- Possibility to enable the feature per user via General User Settings.
- Introduction of a Fair Usage Policy:
- You can track up to 50 users per service-based license and one user per user-based license. The total number of licenses is added up.
- Staggered release, as we monitor data usage and performance.
- A tooltip to show the license usage for Direct Call tracking.
Direct Call Tracking - License usage tooltip
- Change History in Nimbus Admin Portal will reflect updates on this feature.
-
Direct Call Reporting page updated to reflect newest implementation status.
💡 Unchanged: Direct Call Data is available via OData Feed to User Supervisors using the Nimbus Power BI Template (1.122 state).
Other Changes and Improvements
- Data Privacy Service Settings changes are now reflected in the Nimbus Admin Portal > Operations > Change History.
- Companion Service Settings now have dedicated data storage settings.
-
Data Privacy Tenant Settings now has a new “Artificial Intelligence” section with individual consent options for AI-powered Nimbus features. A Tenant Administrator must opt-in to consent before using any AI features that process personal data generated from live calls (e.g. via Transcription or interaction with Virtual Users).
💡Good to know: AI-features which were already configured prior to this change will continue to operate normally, but the (Companion, Virtual User) UIs will be locked against change until Administrator consent was given.
