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.
25 March 2026 - 1.126 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 | 25/03/2026 |
| Australia 01 | 26/03/2026 |
| United Kingdom 01 | 31/03/2026 |
| Switzerland 02 / Germany 02 | 02/04/2026 |
| Switzerland 01 | 05/04/2026 |
| Europe 01 | 08/04/2026 |
| Germany 01 | 12/04/2026 |
Clickable Context Parameters in My Sessions
Parameters on the My Sessions page can now optionally be shown as clickable links, using valid protocols such as msteams://, nimbus-call:, ftps://. This allows users to quickly open websites, start phone calls, or launch the applications with a single click. This saves time, reduces manual copy & paste effort, and helps users complete their contextual tasks more efficiently.
Learn more…
INC Parameters with clickable protocol links
You can generate parameters with protocol-prefix, which will be converted to clickable hyperlinks My Sessions. If the protocol specified in the parameter is recognized, users can directly open relevant resources, apps or engage with external systems.
| Category | Protocol | Description |
|---|---|---|
| Email and Messaging | mailto: |
Mail protocol. Opens the default mail client on the user system and fills in the Email recipient address specified. This is by default used by the following Nimbus System Fields and Parameters:
|
msteams:// |
A Deeplink that opens in MS Teams client. This is by default used by the following Nimbus System Fields and Parameters:
|
|
sip: |
Session Initiation Protocol (VoIP calls) | |
sms: |
Sends SMS via the default messaging app on the user system. | |
| Call Handling | callto: |
Initiates a VoIP call. |
nimbus-call: |
Initiates a Nimbus Call On Behalf1 pop-up. 1💡Note that this link only has an effect once the agent is free to call again. It therefore it makes sense to have "Store Conversation Context Data" enabled on your service to provide the links like an “Instant Callback” functionality. |
|
tel: |
Initiates a phone call. 1💡Note that this link only has an effect once the agent is free to call again. It therefore it makes sense to have "Store Conversation Context Data" enabled on your service to provide the links like an “Instant Callback” functionality. |
|
| Web and Network | http:// |
HyperText Transfer Protocol |
https:// |
Secure HyperText Transfer Protocol | |
ftp:// |
File Transfer Protocol | |
ftps:// |
Secure File Transfer Protocol |
🔎Notes
- These protocols are supported by My Sessions. For a list of supported Assistant protocols, refer to the Click to Call page. Attendant Console will render these protocols as plain text.
- If a parameter contains an unsupported protocol, it is displayed as plain text
- Non‑URL formatted text is displayed unchanged, without hyperlink formatting.
- The copy to clipboard functionality remains intact on protocol links, copying only the actual value (without the protocol).
- When "Store Conversation Context Data" on Extensions Service Settings tab was enabled during the session, users can still see and interact with parameter links after the session was ended.
☝ Nimbus performs no validation of provided protocols that came through via Power Automate Connector. There will also be no security checks of protocols.
🔎Added with this update:
- Parameters page: Added a new “Parameters with clickable protocols” chapter.
- Flow Actions > “Update Task”: Mentioned the option to update existing parameters with new (or different) protocol links.
Task Parallelization: Call on Behalf during After-Call Work
Allowing Contact Center agents to start an Outbound Call (Call on Behalf) during After-Call Work (ACW) helps them to continue follow-up actions without waiting until ACW is finished. This improves efficiency, as agents can reach out to another Nimbus user or service while still completing their after-call tasks. ACW continues until the outbound call is accepted by the destination, ensuring that required documentation and post-call activities are not interrupted. During ACW, no new tasks are assigned to the user, so they can stay focused and avoid overload. This is an improvement to the Task Parallelization feature and helps agents work more efficiently while maintaining focus.
🔎Added with this update:
- Distribution Service Settings: New “Allow Call on Behalf during ACW” toggle (default off).
- Bulk Editing support for this service setting.
- Custom Roles support for the “Call on Behalf during ACW” permission.
Task Parallelization: ACW Support for Audio/Video tasks
Even when handling multiple tasks in parallel, there are often small follow-up actions that need to be completed. With this feature, After-Call Work (ACW) now starts automatically when a (non-parked) Audio/Video session ends, allowing agents to finalize their tasks without interruption. ACW is triggered for all Audio/Video task types and directions, including Consultation Call to services. Parked sessions and other modalities are excluded1. While in ACW, no new incoming Audio/Video sessions are distributed to the user, giving them the time and focus needed to complete post-call work.
🔎Added with this update:
- The above-described behavior automatically takes effect when:
- Task Parallelization is enabled for the User in General User Settings and
- After-Call Work (ACW) is enabled in Distribution Service Settings.
1 When Tasks Parallelization is disabled on your tenant or the individual user, ACW works in the usual way for all types of sessions.
Service System Message support for WhatsApp and SMS/RCS
Service System Messages are automated messages shown to customers or users during specific session events. With configurable system messages for WhatsApp and SMS/RCS, you can standardize what customers see during a service interaction while keeping the main messaging strategy flexible. Most message fields are optional, so you can keep messages simple or add more detail where needed. A new mandatory “Task Limit Reached” message makes sure customers are informed when a service is at task capacity. Delivery and read receipts give you insight into message status, so you can see whether messages are delivered and read and act with confidence.
🔎Added with this update:
With this feature, there will be new configuration options in Nimbus:
- Service System Messages updated for Configuration (Admin Portal) usage, now support both WhatsApp and SMS/RCS Instant Messaging channels.
- Instant Message Handling: The chat window of the previous WhatsApp/SMS IM Session is now shown during ACW on My Sessions page.
- Modalities Service Settings > Instant Messaging: Added optional menus for selecting respective Service System Message entries for each Instant Messaging Integration.
-
Related:
- Updated Use Case - Setting Up a WhatsApp Integration in Twilio to reflect and Service System Messages
- Updated Use Case - Setting Up an SMS/RCS Integration in Twilio to reflect the new RCS specific settings and Service System Messages.
- Limitations and Integration paths updated to include RCS. Please note that RCS is a first implementation with improvements planned for future updates.
Other Changes and Improvements
- The Email Modality now supports HTML rendered tables in email outputs, directly inside the email body.
-
Resources / Playlists Audio Files - Support for WMA audio files has been discontinued. Switching to formats file formats:
wav,mp3is advised. - Data Privacy Service Settings: reordering of options and added KB links. No functional changes with this update.
- Data Privacy Service Settings: Smaller improvements to the Settings UI. Anonymized parameter display for historical calls improved.
- Configuration: Added live KB pages for Service System Messages (Interact, WhatsApp, SMS/RCS) and Direct System Messages (Interact) and updated contents.
- Updated Power BI Template 1.126 with new KPIs and updated filters. Learn more in the Nimbus BI Template Release Notes.