# CopyStorm/Restore 10.65.1

Release Date: 28-Apr-2026

This is a minor feature and bug fix release. As always, existing CopyStorm/Restore configuration files are backwards compatible.

## Patch Levels

|             |                  |
| ----------- | ---------------- |
| 28-Apr-2026 | Original Release |

## Important: Salesforce Username/Password Login Deprecated

Salesforce API version 65 deprecates the SOAP username/password login endpoint. Customers should migrate to an external client application configured with OAuth. Restore jobs using a login type that does not support API 65 will automatically fall back to API 64, and an exception will be logged at the start of each job as a reminder to migrate.

This exception can not be eliminated until OAuth authentication is used. 

### **Salesforce API Version Fallback for Username/Password Logins**

The "Fallback API Detected" error does **not** stop your jobs from running - it is informational, and indicates that CopyStorm/Restore is not able to use the most recent Salesforce API features. The error will be resolved when updating to JWT (or other OAuth) authentication.

Please reference[ Salesforce OAuth Login Types](/frequently-asked-questions/usage/where-does-copystorm-store-passwords/salesforce-oauth-login-types.md).

## Important: Breaking Change - Tracker Database Upgrade

This release includes an upgrade to the H2 database used for restore tracking. Existing tracker databases are not compatible with this version.

## Bug Fixes & Optimizations

### Salesforce API Upgrade

This release updates CopyStorm to use Salesforce **API version 65**.

### Target Organization Visibility Improvement

The target Salesforce organization is now displayed more prominently before a Restore job begins, reducing the risk of restoring to an unintended org.

### Overflow Snapshot Disabled by Default

Overflow Snapshots are no longer included by default during Candidate Scanning. This change improves scan performance for most restore workflows.

### ContentVersion Restore Error Message Improvement

Improved the error message displayed when a ContentVersion restore fails on an unsupported database type (e.g. Snowflake).

### Trace Mode Configuration Fix

Fixed an issue where the "Trace Mode" configuration option was not applied correctly during restore execution.

### Long Object Name Tracker Fix

Resolved an issue where tracker database operations could fail for objects with unusually long names.

### Salesforce API Version Logging

The Salesforce API version is now logged at the start of each Restore job to aid in troubleshooting.

### Rich Text Field Formula Fix

Fixed an issue where the "Rich Text Fields" configuration tab incorrectly included formula fields that contain hyperlinks.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://learn.capstorm.com/copystorm-restore/release-notes/copystorm-restore-10-65-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.