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.
08 July 2026 - 1.131 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 | 08/07/2026 |
| Australia 01 | 09/07/2026 |
| United Kingdom 01 | 14/07/2026 |
| Switzerland 02 / Germany 02 | 16/07/2026 |
| Switzerland 01 | 19/07/2026 |
| Europe 01 | 22/07/2026 |
| Germany 01 | 26/07/2026 |
Distribution Policies: Faster Task Distribution with Level Skipping
Task distribution just got faster. Previously, a Distribution Policy waited at each level until its Activation Time elapsed before escalating — even if nobody was on duty or had the required skills. Now, administrators can configure distribution levels to be skipped automatically when no users at that level match the current condition, instead of waiting out the full Activation Time.
🔎 Added with this update:
-
Distribution Policies - Added new “Skip Levels” option. Allows to configure when to skip levels, e.g. when users are…
- … not “on duty” - e.g. when set Offline / DND / via Profile.
- … not “selectable” - e.g. when already on a task, at capacity, Ringing, Connected, Dialing Out, in ACW.
New "Pickup" Distribution Type for Email, Instant Messaging, and External Tasks
Agents get more control over their workload with the new Pickup distribution type for Email, Instant Messaging, and External Task queue. Now, agents can actively pick up waiting tasks rather than waiting for automatic distribution, deciding for themselves when to take on additional work. For these non-Audio/Video modalities, clicking Pickup accepts the task immediately — no separate Microsoft Teams toast confirmation is required. For skill-based services, current skill and duty profile matching still remain effective.
🔎 Added with this update:
- Workflows > Queue Activities: Now support “Pickup” as Distribution Type for Email, External Task and Instant Messaging queues.
- “Pickup” workflows for all modalities can now be assigned to both Skill-based and MS Teams-based services.
- 💡Notes:
- The “Pickup” button is available on My Overview, Services Overview, Live View, and Attendant Console. It is only active for users who have selected Responsibility Profiles matching with the service's corresponding Distribution Policies.
- Pressing “Pickup” assigns the task immediately, no RONA timeout or Adaptive Cards configuration is available or needed.
Voicemails: Now available for Contact Center Services
Contact Center services now get the same voicemail access experience in the Nimbus UI as the other Nimbus services, closing the historical separation with Enterprise Services. Service users can access voicemails and read transcripts directly in their session view; supervisors get service-level visibility; operations teams can track where voicemails pile up.
By optionally enabling the Nimbus AI Transcriber, voicemails can also be parsed into text, made available in the relevant Nimbus portals. Transcribed Voicemail data can also be integrated into downstream systems via Power Automate for further processing, analytics, or automation.
 |
 |
🔎 Added with this update:
-
A new Voicemails view in the Nimbus UI.
💡 When enabled, the “Voicemail Transcription” option the Modalities Service Settings will attempt to convert the voicemail into text, using the language configured via Speech Recognizers. The transcription will be shown in both Adaptive Cards and the new Voicemails view.
Nimbus Companion Interface: Knowledge Assistant now available in User Portal
Everyone can now chat with the Knowledge Assistant, in both the Nimbus Admin Portal and the User Portal. Answers are generated directly from the Knowledge Base, so users get exactly the information they need, with source links to the KB to follow up when they want more detail. Companion also gets a UI upgrade this release: support for dark mode and multi-language capabilities, and a new side panel that pins to the right of the screen so users can keep following its step-by-step guidance while continuing to work in Nimbus. The pinned panel is fully interactive — users ask new questions and get answers right where they need them — and a single click returns Companion to the full view, to search for and resume older conversations.
🔎 Added with this update:
- Nimbus Companion Interface - Knowledge Assistant is now available in both Nimbus Admin Portal and User Portal. Either can be separately activated in Extensions Tenant Settings tab.
- Shared chat history. Sessions are private to the user-account, persist through both portals, allowing to resume the session as needed.
- Companion features Split- and Full Screen access. Additionally in User Portal:
- UI language support.
- Dark Mode support.
- Knowledge Assistant can also answer in multiple languages if prompted.
💡Note that the Knowledge Base source remains in baseline English, so any literal translations from Knowledge Assistant may not match with Nimbus UI elements.
Workflow Export and Import
Workflows become portable, reusable assets, opening up new practical scenarios: partners can distribute reference workflows to customers for onboarding, teams can promote validated workflows from test to production, and organizations can keep external backups for recovery or compliance. Workflows can now be exported as JSON files and imported into any tenant or cluster. Each export contains the full block topology, wiring, and non-tenant-specific configuration. Tenant-specific references, such as parameters, playlists, and resources, are flagged as missing on import, so users can fill them in for the target tenant before saving.
🔎 Added with this update:
- Workflow Export Import features added to the Workflows, Workflow Templates and Workflow Editing view.
- Users can now Export Workflows and Workflow Templates to a local JSON file directly from the workflow editor.
💡Notes
- If a workflow is based on a workflow template, a dialog appears during export asking whether to export the workflow without the template connection, or to export the template separately as its own file. To prevent Workflow types each have versioning, cannot be mixed or converted on import.
- Importing back into the workflow shows missing (tenant-specific) references.
- Imported workflows are renamed automatically to Imported_<OriginalName>_<YYYYMMDD> and must be saved manually after all missing references are resolved.
Other Changes and Improvements
- Workflow Editing - Selecting an activity now temporarily highlights the connecting line to make visual node connection easier to read.
- On any missed tasks, My Sessions now shows a context menu to start Call On Behalf (Callback) attempts.
💡Only available when the original caller number was stored / not anonymized as per Service Settings. - Virtual Users - Configuration is now split into tabs. This was done to reduce UI complexity and hide unnecessary options, depending on the bot profile chosen.