Latest Release Notes

Stay informed about the latest updates on Nimbus

This page will always reflect the latest Release Notes, recent improvements and changes made to Nimbus.

Other Information 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.nextLink out 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.

🔎@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:

  1. The data client generates a request to the OData service.
  2. The OData service responds.
  3. The presence of @odata.nextLink in the response indicates that the server has more data available.
  4. Clients must continue issuing requests using the provided URL until no @odata.nextLink is 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
  • Reads the page
  • Follows @odata.nextLink
  • Repeats until no link exists
  • Avoids performance-related timeouts from large datasets and “race conditions”
  • Would request huge result sets
  • Assumes pagination is the server’s responsibility
  • APIs run out of memory
  • SQL queries lock tables
  • Refreshes may fail or timeout
 
 

🤔Which Nimbus data is affected?

Impacted OData entities from the Nimbus Reporting Model and Data Aggregation are as follows: 

  • ServiceSessionsAggregates
  • UserSessionsAggregates
  • UserStatesAggregates
  • ServiceSessions
  • UserSessions
  • UnifiedSessions
  • TransferSessions
  • Callers
 
 

🤔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.


15 April 2026 - 1.127 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 15/04/2026
Australia 01 16/04/2026
United Kingdom 01 21/04/2026
Switzerland 02 / Germany 02 23/04/2026
Switzerland 01 26/04/2026
Europe 01 25/04/2026
Germany 01 03/05/2026
Dates subject to change. Refer to https://status.luware.cloud/ > Scheduled Maintenance for the latest status.

Companion Goes to General Availability

With this update, we close the Nimbus Companion preview program and Nimbus Companion becomes generally available to Nimbus customers. Use automated transcription to create a written record of all your incoming audio calls. Let your agents catch up fast on those longer conversations, by providing an AI-powered summarization directly in the UI. With an existing transcript, Companion can also reduce the distracting busywork in your agent's after-call work by automatically suggesting codes and tags best suited to the current conversation.

🔎Added with this update:

  • Companion Service Settings - Companion features will become generally available. The UI might provide these features My Sessions and Attendant Console as additional “Companion” widgets. 
    💡All features are individually configurable per service and by default turned off.
    💡"Live Captioning" features remain in preview and will require an additional license.
  • New optional Companion Features (Transcription, Summarization, Codes & Tags) all become generally available for Companion licensed users. 
  • Codes - New optional “Companion Context” fields for Primary and Secondary Codes, allowing you to describe how Companion should suggest codes automatically after a transcribed inbound audio call.

Nimbus Virtual Users Now Available for Outbound Call with Workflow

INC Preview Feature

This feature is in PREVIEW and may not yet be available to all customers. Functionality, scope and design may change considerably.

Nimbus Virtual Users can now be used in outbound workflows. This enables automated, AI‑driven outbound calls that follow the same configurable workflow logic as inbound scenarios—ideal for proactive customer interactions, surveys, session follow‑ups, or call campaigns without immediate agent involvement.

🔎Added with this update:


Automatic Voicemail Transcription

Save agents from sitting through lengthy voicemail recordings before returning missed calls. With automatic voicemail transcription using Azure Speech Services, transcriptions can now be shown directly in the Nimbus UI (Customer Insights) and delivered as Adaptive Cards in your preferred MS Teams channel, so that agents can quickly skim the message and pick up the phone knowing what the customer needs.

🔎Added with this update:

  • Modalities Service Settings
    • Added new “Voicemail Transcription” Service Setting to automatically transcribe voicemail. This feature is configurable per service.
    • Added a Speech Recognizers option for Voicemail. 
  • With the feature enabled, transcription-enriched Adaptive Cards will be posted to the service's MS Teams channel.
Workflow setup and enabling “Voicemail Transcription” with enabled Speech Recognizer.
Generated Adaptive Card with “Voicemail Transcription”

Keep Track of Initial Entry Point of a Call

When a call passes through multiple hands, critical context can get lost. Nimbus now preserves the original number or identity from the moment a call first enters your system, giving agents transparency into where a call was originally received, even if it was later forwarded to a Luware Nimbus service. This also allows intelligently routing calls to preferred agents, ensuring that customer hear a trusted voice.

💡Some possible application scenarios for this feature are:

  • Preferred User Routing - If a call was originally received by a specific employee, that employee can be prioritized for callbacks or routing decisions.
  • Call flow transparency - Agents immediately understand that the call was not originally intended for them, but was forwarded or escalated.
  • Process Automation - Power Automate flows can branch based on where the call initially entered the organization.
  • Resource analysis - Gain insight into which MS Teams numbers are actually used, even if calls end up in services.
 

🔎Added with this update:

  • System Fields and Parameters - Added new Nimbus System Data: Original Called Number / Original Called Target Type (User / Resource Account / Service).
  • The new Parameters can be shown and used in various areas, such as Nimbus Workflows, Power Automate Connector, My Session Page.

Export Service / User Configuration Data 

Managing audits and operational reviews just got easier. A new export functionality in the Nimbus Service and User Administration lets you capture individual settings as snapshots. This way, you can now keep track of changes over time and see a personal history record. And because the export is powered directly by the internal Nimbus API, you can trust that what you see is what you get: the exact same configuration data — workflows, settings, and licenses.

🔎Added with this update:

Virtual User - New capabilities and quality of life updates

INC Preview Feature

This feature is in PREVIEW and may not yet be available to all customers. Functionality, scope and design may change considerably.

With the addition of a new bot type (based on GPT realtime), Nimbus expands on Virtual User capabilities. The new “AI Workflow” bot type supports a wider array of use cases within workflows, all wrapped in a Nimbus-native integration and UI experience. Nimbus Administrators and Service Owners can leverage external services and formulate more detailed instructions for the AI on how to proceed with this data.

  • Bots - Added extended features with a new bot type “Nimbus AI Services - AI Workflow”.
  • Virtual Users - when selecting the “AI Workflow” bot, new capabilities for Web Requests and MCP servers are unlocked. 
    • AI prompt fields expanded considerably to allow for more detailed instructions.
  • Conversation Handling Activities - “Add Virtual User Activity” now supports a total 3 different bot variants.
    • With the new “AI Workflow” Bot and Virtual user selected, the activity allows to directly engage with a customer in natural conversation. 
    • Added support for Fallback Parameters. These parameters are filled when the AI cannot fulfill a customer request or fails to validate the data necessary to proceed.

Instant Messaging improvements

Improving on the recent SMS/RCS and WhatsApp integration, Nimbus now offers more clarity on the UI and Configuration, clearly highlighting pending interactions, as well as highlighting potential restrictions imposed by the integration channel in use (e.g. remaining or total SMS length). This avoids costly mistakes by either sending too many or no messages to customers as the constraints were hit, or accidentally ignoring a customer's reply in chat.

A red dot will indicate pending messages. The main menu will also show an indicator with the amount of pending messages.
  • My Sessions and Nimbus Main Menu:
    • Instant Messaging tasks, widgets and menus now show "pending interaction" notifications as red bubbles.
      💡Note that this counter increments increments once per pending task, not acting as a total message count. More details can be found under Instant Message Handling > My Sessions.
    • A added validation for Twilio integration messages (WhatsApp, SMS, RCS) to avoid message sending failures due to oversized messages. Chat Widgets in the My Sessions UI will now show message limits and warnings, also display links to the KB for further information.
    • Conversation Handling Activities > “Message" - Added notes activity behavior when message length (imposed by the channel integration and protocol) is exceeded. The activity will be skipped e.g. when Parameters resolve into messages that would exceed the limit.

Other Changes and Improvements

Table of Contents