Riva 2026.3 Cloud and On-Premise Release

Grace Wannapongsai
Grace Wannapongsai
  • Updated
Deployment Model Release Date Details
Riva On-Premise Aug 20, 2026
Riva Cloud Jul 21, 2026 — Release Candidate Channel (z-pods)
Aug 6, 2026 — Pre-Release Channel (y-pods)
Aug 17-21, 2026 — Production

Interested? Schedule a consult.

New Features!

Available for Riva Cloud and Riva On-Premise

AI-Powered Email Thread Summarization

Riva now supports AI-generated summaries of synchronized email threads, helping users quickly understand key decisions, action items, and conversation context without reviewing the entire thread. Summaries are stored in Salesforce as Email Message and remain available independently of raw email retention policies, helping improve productivity and support compliance requirements.

User Guide can be found here. 

 

Salesforce Refresh Token Rotation (RTR) Support

Riva now supports Salesforce Refresh Token Rotation (RTR), enabling compatibility with Salesforce's enhanced OAuth security model. Customers can enable Refresh Token Rotation without impacting connection reliability or long-running synchronization.

  • Improved Authentication Reliability: Automatically captures and persists newly issued refresh tokens, ensuring uninterrupted authentication during token rotation.
  • Support for Modern Salesforce Security: Fully supports Salesforce organizations and connected apps with Refresh Token Rotation enabled.
  • Enhanced Multi-Node Support: Coordinates credential updates across distributed deployments to prevent token conflicts and authentication failures.
  • Seamless Connection Recovery: Improves authentication recovery following token expiration, reducing manual intervention and minimizing synchronization interruptions.

Note: If Refresh Token Rotation is enabled on an existing Salesforce connected app or organization after a connection has already been authorized, the affected connection must be reauthorized once. This is required because Salesforce invalidates the previous refresh token and cannot be completed automatically.

 

Applies to Riva On-Premise only

Upcoming Salesforce SOAP API Authentication Changes (17978)

Salesforce has announced the retirement of the SOAP API login() method beginning with the Summer '27 release. To prepare for this change, Riva has removed the username/password authentication option from the On-Premise user interface and continues to support OAuth as the recommended authentication method. Customers currently using username/password authentication should plan to migrate to OAuth before Salesforce's retirement date to ensure uninterrupted connectivity.

 

Applies to Riva Cloud only

AI Assistant Added to Riva Cloud

Riva has added an AI Assistant to Riva Cloud, which allows customers to search our knowledge base directly from Riva Cloud to help with any questions they may have. This is accessible through the 'Ask AI' button visible on the bottom right hand corner of Riva Cloud. Any queries will search our knowledge base for relevant solutions and articles that may assist you.

In addition, we have added functionality to the support form on the 'Contact Us' page, where your problem will be searched to see if there is a relevant knowledge base article that can help assist you. If not, you are able to submit a support ticket and someone from Riva will contact you.

 

Enhancements

Available for Riva Cloud and Riva On-Premise

Add Riva to Microsoft’s EWS Allow List

Riva recommends that Exchange Online customers add Riva to Microsoft’s EWS allow list by the end of August 2026. This provides a continuity safeguard that may extend EWS access until April 2027 while migrations are completed.

Microsoft Graph remains the required long-term path. Allow-listing Riva should be treated as a temporary risk-reduction measure, not a reason to delay migration before the October 2026 EWS retirement milestone.

To learn more, click here. 

Exchange Graph Sync Enhancements

This release expands Microsoft Graph support across CRM record creation, mailbox processing, folder synchronization, recipients, attachments, and administrative operations.

Feature & Enhancements Description 
Custom email folder modules   
 		 Enables configured Outlook folders to create corresponding records in Salesforce when users move emails into them.
Orders module    Adds support for creating CRM Order records through the Create New Orders folder, including related Assign To folder operations.
Subfolder synchronization Enables synchronization of Inbox subfolders and additional calendars.
Folder and calendar exclusions Allows administrators to exclude selected email folders or calendars from synchronization.
Lost-and-found folder override Allows a configured mailbox folder to be used for lost-item processing.
Email source detection Uses internet message headers to determine whether an email originated as a sent or received item.
Failed email visibility Marks an Exchange email as unread when Riva cannot create the corresponding CRM record.
Link-state assignment Adds Riva link-state information to newly created Exchange email items.
Link-state check controls Allows link-state validation to be disabled globally or separately for Inbox and Sent Items.
Auto-reply matching Supports regular-expression rules for identifying and processing automatic replies.
Unsendable recipient loading Loads recipients marked as unsendable on custom appointments when they match an existing CRM user.
Recipient override behavior Removes a matching sendable recipient when an unsendable version of the same recipient is found.
Inline-image exclusion Allows embedded images in an email’s HTML body to be skipped during CRM synchronization.
Custom inline-image matching Uses object-specific regular expressions to identify additional attachment types that should be treated as inline images.
Property-tag exemptions Prevents configured Exchange property tags from being retrieved through Microsoft Graph.
Batched sync-configuration removal Retrieves and deletes sync configurations in smaller batches to reduce failures caused by Graph access-token expiration.
Cleanup progress logging Records batch counts, processed items, failures, and retries to improve troubleshooting and operational visibility.

 

Applies to Riva On-Premise only

20199 Salesforce Username/Password Authentication Deprecation

To align with Salesforce's retirement of the SOAP API login() method, Riva has deprecated support for username/password authentication in the On-Premise user interface. Customers should transition to supported authentication methods for Salesforce connections. Documentation has also been updated to reflect Salesforce's authentication changes.

Learn More

19214 Configurable EULA Validation for the Riva On-Premise Application

Riva now provides an option to bypass the End User License Agreement (EULA) validation when launching the Riva On-Premise application. This enhancement simplifies deployment and administration in managed environments where interactive EULA acceptance is not practical, such as remote management servers.

 

Applies to Riva Cloud only

21258 Updated Tab Styling on Synchronization Settings Page

Riva has made some UI improvements to the appearance of the tabs that are visible on the Synchronization Policy Settings page to modernize the application and align with other Riva products.

 

21380 Enabled support for Salesforce Proof Key for Code Exchange (PKCE) in Riva Cloud

Riva has made a change to Riva Cloud in order to support new security requirements from Salesforce.

The use of PKCE to protect OAuth Authorization Code login flows is now required for all Salesforce client apps. This feature has been supported by Salesforce for many years as an optional feature, but it is now considered an essential industry security practice for OAuth 2.0.

Riva has added support for this on Riva Cloud if this option is enabled on Salesforce.

This change affects both the creation of new connections and the revalidation of existing Salesforce connections.

 

Bug Fixes

Available for Riva Cloud and Riva On-Premise

21595 Calendar Re-initialization Metadata Synchronization

Riva resolved an issue in which calendar items could be skipped after a Clear Metadata calendar re-initialization. Stale synchronization metadata could cause newly created calendar items to be incorrectly identified as already synchronized. This fix ensures metadata is properly reset during re-initialization so that new calendar items are evaluated and synchronized as expected.

 

Applies to Riva On-Premise only

21566 Policy Loading Reliability in Remote Administration Server

Riva resolved an issue where the Remote Administration Server (RAS) could fail to load policies if a policy referenced a missing file. This fix ensures invalid file references are handled gracefully, allowing the service to continue loading valid policies without interruption.

21037 EWS OAuth Token Refresh After .NET 8 Migration

Riva resolved an issue where EWS OAuth token refresh could fail after migration to .NET 8, causing Exchange sync failures after token expiry. This fix ensures OAuth token renewal completes successfully and Exchange sync continues without interruption.

20871 Complete Create Event Logging for Attachment Synchronization Errors

Riva resolved an issue where CREATE events were not logged if an attachment synchronization error occurred after an item was successfully created in the CRM. This fix ensures CREATE events are consistently recorded, improving the accuracy of synchronization logs and simplifying troubleshooting.

20106 Appointment Category Handling for Salesforce Sync

Riva resolved an issue where some appointments could sync to Salesforce even when they did not meet the expected category or sync qualifier requirements. This fix ensures appointments without the required categories are skipped as expected, preventing unintended records from being created in Salesforce.

20190 Salesforce Web API Record Type Retrieval

Riva resolved an issue where Salesforce Web API queries could incorrectly remove valid RecordType.Name fields when filtering invalid query parameters. This fix ensures valid record type information is retained and returned correctly during synchronization.

20106 Appointment Synchronization Criteria

Riva resolved an issue where some appointments could be synchronized to Salesforce even when they did not meet the required synchronization criteria. This fix ensures appointments without the appropriate categories or sync qualifiers are correctly skipped, preventing unintended records from being created in Salesforce.

 

Applies to Riva Cloud only

18614 Resolved Bug with Sync Peak Times

Riva resolved an issue when setting Sync Peak Times: if the time span exceeded 12 hours, the policy could not be saved. We have made a fix to ensure that time spans greater than 12 hours are now supported when setting the Sync Peak Times in the Synchronization Policy Settings page under the 'Schedule' tab.

Riva Cloud Deployment Details

Riva Cloud Sync and Web (rivacloud.com) are scheduled to be upgraded to 2026.3 between August 17 and 21, 2026. To ensure a smooth transition, we are providing the following schedule:

Riva Cloud Sync Release

  • Release Candidate Channel Upgrade (z-pods): July 21, 2026, after regular business hours
  • Pre-Release Channel Upgrade (y-pods): August 04, 2026, after regular business hours
  • Release Channel Upgrade (x & main pods): August 17-19, after regular business hours.
    • August 17 (Sync)
      • au1x
      • eu1x
      • na4x
      • na5x
      • na6x
      • na8x
      • na10x
      • edupx
    • August 18 (Sync)
      • au1
      • na4
      • na5
      • na6
      • edup
    • August 19 (Sync)
      • eu1
      • ca1
      • na8
      • na10

Riva Cloud Web (rivacloud.com) Release

  • Pre-Release Channel Upgrade: August 05, 2026, after regular business hours
  • Release Channel Upgrade: August 20-21, 2026, after regular business hours.
    • August 20 (rivacloud.com)
      • Australia
      • Canada
    • August 21 (rivacloud.com)
      • Europe
      • United States

Note that you can determine which pod and data residency your account resides on by logging into your Riva Cloud account, navigating to “Manage Account” and selecting “Account Summary”. In the top right, under the header Data Residency Region /Configuration Pod.

Testing Period

You will have approximately three (3) weeks to test this release on the pre-release channels before it is rolled out to the release channels. 

Next Steps

  • Testing: Conduct thorough testing in your lower environment after the July 21 upgrade. If you are unsure whether you have a lower environment on the pre-release channel, please contact the Technical Support team here.

Potential Impacts

The upgrade will be completed after regular business hours. During the upgrade, there could be a short window of service disruption (10-20 minutes).

Support
For any questions or concerns, please contact the Technical Support team here.