Riva Insight 2026.1 Release Notes

Curtis Massie
Curtis Massie
  • Updated

Riva Insight 2026.1 Which version do I have?

Riva Insight Cloud

The 2026.1 release will have staged rollouts to environments across preview and live:

  • Preview: From January 07, 2026 to February 11, 2026.
  • Live: From January 28, 2026 to March 13, 2026.

Riva Insight On-Premises:  

  • There is no planned 2026.1 release for Riva Insight On-Premises. Use the most recent 2025.2 release for all the latest hotfixes.

Windows Add-in (Legacy Outlook VSTO Plugin) Customer?

Windows Add-in versions more than 2 versions behind are not guaranteed to be compatible with this release.

 

Insight Cloud Upgrade to .NET 8

Riva Insight has been upgraded to the Microsoft .NET 8 technology. This update improves performance, boosts security, and lays the groundwork for future enhancements—all working quietly behind the scenes to make your experience better.

Key Benefits for End-Users

  • Quicker Load Times: Pages and features open faster, reducing wait time and improving overall flow.
  • Smoother Interactions: The app handles tasks and processes more fluidly, so users experience fewer delays or glitches.
  • Improved Reliability: Fewer outages or disruptions mean users can count on the system being available when they need it.
  • Enhanced Security: Updates to underlying technology help protect user data and privacy, even if those updates are invisible.
  • Consistent Experience Across Devices: Modern architecture improves cross-platform compatibility, so the experience feels right whether you're on desktop, tablet, or mobile.
  • Future Enhancements Delivered Faster: New features and updates roll out with minimal disruption—users benefit sooner without needing to wait through long upgrade windows.

What to Expect

  • Some users may be asked to log in again due to updated security measures.
  • No changes to how you use the app—just better performance under the hood.

 

New 'Pending' Outlook Category for Tracked Items

Riva is improving sync speed for tracked items in Outlook Classic by applying category tags. The category tags help Outlook prioritize updating the local cached copy of the message or meeting to the server. Users can also easily identify items that have been tracked and not synced to CRM by the presence of the pending tag. These changes were available in Riva Insight 2025.2 (off by default) and will be enabled by default in Riva Insight 2026.1.

What You Need to Know

  • This update improves the time it takes for Outlook to update the tracked item from the Outlook Classic mail client to the mail server resulting in a shortened sync speed for tracked items.
  • Tracked items will show a Sync Category; pending items will show a Pending category.
  • These categories help Outlook prioritize syncing and also indicate sync status.
  • No action is required. Riva is applying this change automatically.

For more Information, check out Improvements to Syncing Tracked Emails and Meetings in Outlook Classic with Riva Insight.

 

Updated Branding: New Logo, Styles, and Colors

What’s new
Riva Insight has been refreshed to align with Riva’s new brand identity. This update includes:

  • A new Riva Insight logo
  • Updated color palette across the application user interface
  • Updated buttons and text styling across the application user interface

Updated Areas

  • Riva Insight Logo - New Riva logo is displayed across:
    • Login screen
    • Application header
    • Settings pages
  • Updated Color Palette and Text Styling - The application color scheme and text styling have been refreshed to match the new branding in following elements:
    • Header and navigation colors
    • Buttons (primary / secondary)
    • Links and highlights
    • Toast messages
    • Section headers and accents

Why this matters

  • These changes ensure visual consistency with our latest branding while maintaining the same functionality and workflows you’re familiar with.

Impact to users

  • No functional changes. All features, configurations, workflows, permissions, and data remain the same.

 

Bug Fixes and Other Enhancements

  • 2025.2.10.3210 - Added the ability to view meeting CRM cards for items tracked by other users to custom modules.
  • 2025.2.10.3255 - Added the ability to auto-set fields with a field from a CRM lookup.  For example, when creating new task record, populating the assignee with the Salesforce user of the Insight logged in user.
  • 2025.2.10.3276 (2025.1.10.3275) - Added a interval between recipient lookup to limit crashing with the Windows Add-in while Outlook is being moved or resized and recipients being retrieved in Insight due to the UI thread being shared with WebView2.
    • CompanySettings.xml:
    • <add key="Insight.WinAddin.CurrentItemRecipients.LookupIntervalMs" value="3000" />
  • 2025.2.10.3286 - Added the ability to sync items to custom objects using the mail item message id.
  • 2025.2.10.3328 - Fixed issue with legacy Track in CRM where the OnSend prompt was not aware of meetings that were tracked using 'Track and Send' and still displayed a prompt when meeting was updated later. 
  • 2025.2.10.3409 - Updated links to KB articles to point to Riva's new KB.
  • 2025.2.10.3413 - Fixed a bug where Track onc CRM  Module Dropdown Ui Controls where being auto-populated, even when configured to not auto-populate.
  • 2025.2.10.3439 - Fixed a bug where the track qualifiers were lost after tracking then moving off the email, resulting in the email not getting picked up by Riva Sync.
  • 2025.2.10.3467 - Changed the location up the unmatched contacts to appear above the track form instead of below (requires unmatched contacts to be enabled for the track view - disabled by default).
  • 2025.2.10.3495 - Added an option to disabled the Track button for new emails and meetings (while still keeping Track and Send).
    • CompanySettings.xml:
    • <add key="Feature.Track.TrackButtonForNewMeeting.IsEnabled" value="True" /> 
<add key="Feature.Track.TrackButtonForNewEmail.IsEnabled" value="True" />
  • 2025.2.10.3499 - Added a configurable option to set the sync category when items are tracked in the Inbox or Sent Items folders, reducing the time it takes for the Outlook client copy of the mail item to update to the mail server, which in turn allows Riva Sync to pick up and process the tracked item sooner.

    • CompanySettings.xml:

      <add key="Feature.Track.TrackStateService.SetCategoryWithOfficeJs.IsEnabled" value="True" />

    • TrackConfiguration.xml:

      <add key="Track.MailItems.SetSyncCategory.Email" value="true" />
  • 2025.2.10.3599 - Added a new setting to the ModuleUI control that will automatically populates a field in Track in CRM when a record (such as contact or opportunity) is created through the creates form.
    • <IsAutoSelectNewCreated>true</IsAutoSelectNewCreated>
  • 2025.2.10.3531 - Changed Sales Engagement to load customer app using settings from Riva Cloud instead of a hard-coded configuration settings.
  • 2025.2.10.3579 - When a contact is created from unmatched contacts, the contact is now removed from the unmatched list in the context view.
  • 2025.2.10.3572 - Added the ability to auto-populate a ModuleUI control in Track in CRM with internal attendees where the internal attendees are represented by a custom object.
  • 2025.2.10.3581 - Fixed an issue where an auto-save draft is created when a control is being auto-populated by a query lookup.
  • 2025.2.10.3695 - Added a warning message when trying to track in another users' mailbox as a delegate when the delegate does not have modify permissions. Previously the page would not finish loading.
  • 2025.2.10.3719 - Fixed an issue where the logs were showing the login method as Salesforce when using Login with Microsoft.
  • 2025.2.10.3734 - Fixed an issue when to auto-populating a ModuleUI control in Track in CRM with internal attendees where the internal attendees are represented by a custom object, if the organizer was removed, it was re-added if the user reloaded the side-panel.
  • 2025.2.10.3761 - Added the ability to custom css style to the label and message of info controls in Track in CRM.
    • <Label Style="color:#FF0000;font-size:1.2rem;font-weight:bold;font-family:Arial, sans-serif;">
  All features on label
</Label>
<Message Style="color:#FF0000;font-size:1.2rem;font-weight:bold;font-family:Arial, sans-serif;">
  All features on message
</Message>
  • 2025.2.10.3761 - Added the ability to custom css style to the unsaved changes message in Track in CRM.
    • <add key="Track.Draft.ButtonStyle"
     value="color:#FF0000;background-color:#FFFF00;font-weight:bold;font-size:1rem;border:1px solid #000000;" />
<add key="Track.Draft.ButtonStyle"
     value="font-family:'Segoe UI',sans-serif;font-size:1.2rem;" />
<add key="Track.Draft.ButtonStyle"
     value="background-color:#EEE;border:1px solid #333;" />
  • 2025.2.10.3766 - Fixed an issue when creating a contact in Insight outside of Outlook, the page would hang.
  • 2025.2.10.3782 - Added a configurable option to custom lock expressions, allowing the track form to be locked based on field or user information.  For example, after an item has synced, lock if the user is an attendee, but not if the user is the organizer.
  • 2025.2.10.3823 - Fixed an issue where unmatched contacts was used the url-encoded value of the email address, preventing users from creating a contact from unmatched contacts.
  • 2025.2.10.3872 - Fixed an issue where the organizer was being auto-populated, even though the organizer was not included in the recipient type list to auto-populate.
  • 2025.2.10.3875 - Removed fallback to server-side MSAL when using Nested App Authentication, allowing for Graph Apps to be used without requiring a secret or certificate.
  • 2025.2.10.3894 - Fixed and an issue where auto-setting a date and/or time in the create form was not being updated in CRM due to the conversion to UTC.
  • 2025.2.10.3905 - Fixed an issue where the Insight panel stays blank when switching emails when in the create or update view
  • 2025.2.10.3980 - Fixed an issue where a related record that was deleted in CRM was still showing in the Track view when loading a previously tracked item.
  • 2025.2.10.3997 - Fixed an issue where a synced item that was not tracked was not loading the CRM data into the Track view.
  • 2025.2.10.4015 - Added logging of the Salesforce custom domain from Riva Cloud when using Login with Microsoft to aid with troubleshooting.
  • 2025.2.10.4029 - Fixed issue with accounts with multiple profiles where the Login Profile selector with Login with Microsoft is only sending the login profile up to the first space, prevent users from logging in.
  • 2025.2.10.4020 - Added a configurable option to set a 'pending' category when items are tracked or re-tracked, reducing the time it takes for the Outlook client copy of the mail item to update to the mail server, which in turn allows Riva Sync to pick up and process the tracked item sooner.  The 'pending' category is removed after being processed by Riva Sync.

    • CompanySettings.xml:

      <add key="Feature.Track.TrackStateService.SetOutlookPendingCategory.IsEnabled" value="true" />

    • Riva Sync - CRM Connection

      <add key="Sync.Crm.PendingCategoryName" value="Pending" />
  • 2025.2.10.4102 - Fixed an issue where a bad merge with a progressive web app setting caused the Insight side panel to be not load and only show a spinner on the loading screen.
  • 2025.2.10.4104 - Fixed issue where a response from Graph that is undefined or invalid caused Insight to be stuck with a spinner on the loading page.
  • 2025.2.10.4150 - Fixed an issue where Insight would be stuck with a spinner on the loading page when Insight is used outside of an Outlook client.
  • 2025.2.10.4280 - Added masking to refresh tokens logged in the browser console logs. 
  • 2025.2.10.4310 - Allow Graph connection strings to no longer require the client secret, allowing graph apps using Nested App Authentication to not require secrets or certificates.
  • 2025.2.10.4381 - Allow lock expressions to support custom modules.
  • 2025.2.10.4400 - Addressed a bug where the Related tab was not appearing for Outlook Mobile.
  • 2025.2.10.4417 - Addressed a UI bug where the Login Profile selector would show older/cached values before  showing the correct login profiles.
  • 2025.2.10.4453 - Addressed an issue when sometimes tracking an occurrence, the track view remains displayed and does not show the related tab.
  • 2025.2.10.4472 - Fixed an issue when autopopulateing a multi-module dropdown control is creating an autosave draft.
  • 2025.2.10.4534 - Fixed an issue when tracking, the pending back does not appear right away on the related tab.
  • 2025.2.10.4537 - Fixed an issue where the track view is not locked after tracking when using the GlobalId configuration to load crm records for the track view.
  • 2025.2.10.4634 - Added a configurable option to disable tracking of meeting occurrences. THis setting should be used when the Riva Sync policy is configured to only sync the first occurrence of a recurring series.

    • CompanySettings.xml:

      <add key="Track.MeetingOccurrence.IsEnabled" value="false" />
  • 2025.2.10.4650 - Fixed the key for customizing the name of the related tab from 'Insight.Tab.Name' to 'Insight.Tab.Name.Related'.
  • 2025.2.10.4722 - Changed the "populate" button to reset the auto-populated values. If there are already auto-populated values, there is a prompt asking for confirmation to reset the populated values. Previously, the populate button would not clear or reset if there were already populated values.
  • 2025.2.10.4754 - Fixed an issue with legacy track where the check for changes in a meeting was omitting the subject, resulting in repeated Outlook prompts to save or discard.
  • 2025.2.10.4774 - Added new configuration for internal domains to support matching/auto-populating as internal when the user domain does not match contact domain.
  • 2025.2.10.4842 - Fixed issue where the 'pop-out' dialog for meeting notes was showing an empty screen.
  • 2025.2.10.4891 - When using the GlobalId to load CRM records for recurring series occurrences, the start date is now being used to ensure the correct occurrence is loaded.
  • 2025.2.10.4895 - When using the GlobalId to load CRM records for recurring series occurrences, the GlobalId is retrieved from the series master.
  • 2025.2.10.5008 - Added a configurable option to enable or disable the Track and Track and Close buttons for existing meetings (as Organizer).
    • CompanySettings.xml:
    • <add key="Feature.Track.TrackAndCloseButtonForExistingComposerMeeting.IsEnabled" value="True" />
<add key="Feature.Track.TrackButtonForExistingComposerMeeting.IsEnabled" value="True" />
  • 2025.2.10.4979 - Fixed issue with legacy track where the user is stuck on the Outlook server delay messages, even after retrying.
  • 2025.2.10.5167 - Addressed issue when switching between multiple Outlook users by ensuring the current user profile matches the Nested App Authentication profile.
  • 2025.2.10.5273 - Show the Series or Occurrences badges on all tabs by default, instead of just the track tab. Added configurable option to hide the badges.
    • CompanySettings.xml:
    • <add key="Insight.Tab.Related.RecurrenceBadge.IsEnabled" value="true"/>
<add key="Insight.Tab.Track.RecurrenceBadge.IsEnabled " value="true"/>
<add key="Insight.Tab.Actions.RecurrenceBadge.IsEnabled" value="true"/>
  • 2025.2.10.5376 - Added configurable options to set the default tab.

    • Examples - CompanySettings.xml:

      <!-- Options: Related,Track,Actions -->
<!-- Global Settings-->
<add key="Insight.Tab.Default.New" = "Track">
<add key="Insight.Tab.Default.Existing" = "Related">
<!-- Or set per type of item -->
<add key="Insight.Tab.Default.New.Email" = "Actions">
<add key="Insight.Tab.Default.Existing.Email" = "Related">
<add key="Insight.Tab.Default.New.Appointment" = "Track">
<add key="Insight.Tab.Default.Existing.Appointment" = "Related">
  • 2025.2.10.5325 - Fixed an issue for when a user tries to create and track a new meeting on the calendar for which user has delegate permissions, and shows an "changes detected" error.
  • 2025.2.10.5383 - Fixed an issue with the Windows Add-in where the pending tag is still displayed after a tracked items has been synced.
  • 2025.2.10.5385 - Change auto-populate to remove an auto-populated contact when removed from the recipient or attendee list in Outlook. This will not remove the contact if manual edits were made to the list or if there is an autosave draft.
  • 2025.2.10.5405 - Updated the configurable option to set the sync category on new (Track and Send) items in addition to when items are tracked in the Inbox or Sent Items folders, reducing the time it takes for the Outlook client copy of the mail item to update to the mail server, which in turn allows Riva Sync to pick up and process the tracked item sooner.

    • CompanySettings.xml:

      <add key="Feature.Track.TrackStateService.SetCategoryWithOfficeJs.IsEnabled" value="True" />

    • TrackConfiguration.xml:

      <add key="Track.MailItems.SetSyncCategory.Email" value="true" />
  • 2025.2.10.5440 - Fixed an issue with authentication flow for business units/group names with space character.
  • 2025.2.10.5453 - Fixed an issue with showing meeting CRM cards in delegated calendars.
  • 2025.2.10.5466 - Changed Manifest ID to use only lowercase letters.
  • 2025.2.10.5509 - Changed Insight URL and default URL to use only lowercase letters to prevent tracking issues.
  • 2025.2.10.5794 - Improved Track State Service performance in polling process of tracked, but un-synced items. 
  • 2025.2.10.5912 - Fixed an UI issue in showing double "x" close buttons in pop-up windows.
  • 2025.2.10.6050 - Fixed an issue in detecting user's timezone.
  • 2025.2.10.6197 - Improved user authentication flow increasing reliability.  
  • 2025.2.10.6305 - Improved Insight logging process to increase the performance.
  • 2025.2.10.6339 - Fixing performance related issues related to caching.
     

Post-release Bug Fixes and Enhancements

2026.1.0.453

  • 20765 - Fixed an issue with LogRocket preventing Riva Insight from loading
  • 20688 - Fixed an issue with loading Riva Sync configuration within Insight about page
  • 20599 - Improved logging to remove duplicate logs
  • 20555 - Improved properties inspector to include GRAPH item for faster diagnosis
  • 20107 - Fixed an issue with loading user information where user lacks access to Salesforce profile object

2026.1.0.447

  • 20625 - Fixed an issue with GRAPH calls timing to prevent infinite loading in Related tab
  • 20119 - Improved Insight logging for failures including GRAPH requests, Office.js runtime errors, initialization failures, view render, and consequent feature degradations

2026.1.0.444

  • 20418 - Improved detection of Office.js initialization to reduce instances where the related, track or actions tab appears empty.
  • 20419 - Fixed issue where the CRM card for a meeting series or occurrence is not displayed after changing the meeting schedule.
  • 20039 - Records that have been deleted from CRM can now be re-tracked. To enable, add "Feature.Track.AllowRetrackDeletedRecords" to the companysettings.xml configuration file.

2026.1.0.436

  • 20415 - Added a retry to handle GRAPH API updates to a mailitem when an ErrorIrresolvableConflict error is encountered (item has changed since last retrieved).
  • 20416 - Added an exponential retry when a GRAPH API throttling limit (HTTP 429 - Too Many Requests) error is encountered.
  • 20374 - When logins are restricted in Salesforce, a more informative error message is now displayed.
  • 20394 - Fixed issue with the diagnostics health check returning null for WebApi.
  • 20030 - Updated the Sync Configuration diagnostic page to eliminate redundant information
  • 20030 - Reduced GRAPH API throttling limit (HTTP 429 - Too Many Requests) errors by reducing the number on concurrent GRAPH API calls.
  • 20030 - Added a retry when retrieving a mail item with GRAPH API returns a 404 error due to handle a bug encountered with the Microsoft GRAPH API.
  • 19694 - Improved error messages when encountering connectivity errors with the Enhance Track in CRM (TSS) data store.
  • 20402 - Improved encoding of Javascript in Riva Cloud Auth razor pages for consistency.
  • 20323 - Improved check for detecting compose mail items in Outlook to prevent displayReplyForm null errors from being logged.
  • 20323 - Added additional checks to wait for the Office API to load before making Office calls.
  • 20093 - Fixed the flow of the diagnostics health check to ensure the checks run in proper sequence.
  • 20092 - Fixed diagnostics health check to validated contact discovery service when supported instead of just enabled.
  • 20118 - Improved back-end logging for WebApi and Sales Engagement service calls.
  • 18922 - Improved Email Generation and Riva for Agentforce endpoint security.
  • 20345 - Addressed issue where Riva for Agentforce showed a blank screen when opened.
  • 20239 - Improved MSAL Auth handling for mailboxes with multiple accounts to ensure the GRAPH API calls are made using the correct context.

2026.1.0.422

  • 19431 - Renamed Riva Copilot to Contact Discovery
  • 19612 - Ensured that subsequent calls for an access token when there is a Conditional Access Policy (CAP) claims challenge obtains a new token due to a MSAL bug that does not properly cache new tokens.
  • 19140 - An error will now be shown when the trackstate office custom property unexpectedly exceeds 2500 characters.
  • 20116 - Fixed issue with legacy track where a conflict with the server and client version of a mail item results in the server copy overwriting the client copy and reverting or removed the sync properties and categories on the mail item.
  • 19785 - Improved logging to better identify the flow and source of the issue.

2026.1.0.412

  • 20111 - Addressed issue where the Windows Add-in version was not displayed correctly on the about page.
  • 20194 - Fixed issue where all client-side logs sent to the server were treated as warnings instead of the expected log level.
  • 20181 - Fixed issue Windows add-in not showing the disconnect from Salesforce option or connected status.
  • 19809 - Updated the health checks for Insight microservices to show the start time and uptime.
  • 20117 - Fixed an issue with the Windows Add-in that causes the track autosave draft to hang, and prevent tracking.

2026.1.0.407

  • 19572 - Improved the warning for track when the corresponding sync configuration was missing (not enabled).
  • 19925 - Fixed the health check that showed a 500 error if the Insight application was not initialized first.
  • 19872 - Added the Riva Cloud Auth url to the diagnostics health check.

2026.1.0.401

  • 19685 - Add a Sync Configuration diagnostics page to the about page to view the current sync configuration and allow for a forced reload of the syncconfiguration.
  • 19700 - Improved the handling and display of GRAPH API auth errors.
  • 18693 - Centralized static assets into a shared library to be used by the Insight and Insight auth services.

2026.1.0.393

  • 19572 - Resolved an issue with that allows mail items to be tracked even though the corresponding sync configuration was missing (not enabled).
  • 18906 - Addressed issue when tracking an meeting as an attendee tries to close the mail item (the office API does not support automatically closing the api when an attendee).
  • 18361 - Updated Contact Discovery to not show create or update options for a contact if the user does not have create or update permissions.
  • 19575 - Removed check for Sales Engagement feature check when Sales Engagement is not enabled.
  • 19402 - Removed legacy code for Insight Bookings OnSend handlers.
  • 19399 - Reclassified loglines that were warnings but treated as errors.

2026.1.0.378

  • 19385 - Improved the diagnostic health check for Enhanced Track in CRM to perform CRUD operations against the track state data store.
  • 19400 - Removed 'Sales Engagement Server Address' warning from logs as the server address now comes from Riva Cloud.
  • 19475 - Updated the StackExchange.Redis version to 2.10.1 for better performance with Valkey serverless.
  • 19225 - The cache duration for the user timezone has been extended to ensure it maintained longer than the local user cache.
  • 19278 - Fixed issue where the Insight Settings could not be accessed from Riva Cloud.