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 Power Automate Connector Change Notice

📆Upcoming change: New Power Automate connector user role validation

We're introducing an important enhancement to the Nimbus Power Automate Connector, rollout planned on 15th of January 2026. This update is designed to improve security and ensure that flows are only triggered by users with valid permissions.

☝What is changing: 

  • Currently, users must hold a Power Automate Role in Nimbus - either Service Owner or Administrator. The role is validated when creating a flow.
  • With this upcoming update, an additional step will be introduced, validating roles at each execution of a flow. This effectively prevents flow-execution by users who no longer have the appropriate access.

✅Action required: We recommend for all our customers using the Power Automate Connector to review and confirm their flow configuration to avoid any disruption. Keep in mind that the new validation will not just check the role but also the Organization Unit scope under which the user operates. Any later changes in the user's OU scope will also affect existing flows  - e.g. the services that the user can see and impact.

 

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
Dates subject to change. Refer to https://status.luware.cloud/ > Scheduled Maintenance for the latest status.

Attendant: Transfers and Consultation Calls for Outbound Sessions

Outbound call and Call on behalf now support various transfer scenarios and destinations

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

Concluded (Historical) Sessions for both inbound and outbound PSTN calls can now be anonymized using the new “Caller Anonymization” feature.

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

Table of Contents