Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 58 Next »



Version 5.3.2 Release Notes

Version: 5.3.2.3623

Release Date: February 2, 2023

DryvIQ Migrate version 5.3.2 was available on February 2, 2023. This maintenance release focused on performance enhancements and bug fixes. Learn more about the release below. For detailed information about features mentioned, refer to the DryvIQ Migrate Documentation Center.

Enhancement

  • Box changed the way it reports rate limit errors, so DryvIQ updated our Box connector to reflect this change. Rate limits will be reported with the following error: Request rate limit exceeded, please try again later [code=rate_limit_exceeded].

  • New indexes were added to the TransferItemEmbeddedLinks table to improve query performance and minimize issues with connecting to the database.

  • New indexes were added to the permissions tables to improve performance and solve timeout issue in some environments.

Fixes

  • Updates were made to the CLI to correct an issue that prevented the SkySync CLI (DryvIQ’s CLI interface) from running on Node JS version18 and higher. Users having an issue running the CLI must update their SkySync CLI to 5.3.2 to correct this issue.

  • A fix was made to ensure cancelled jobs do not continue to run.

  • An update in Fiddler Classic and Fiddler Everywhere caused an issue that prevents .SAZ FiddlerCore output files from being opened. DryvIQ made changes to its integration with FiddlerCore to work around the issue and ensure the .SAZ files can be viewed.

  • Updates were made to the Microsoft Office 365 connector to ensure the Set Tenant Level Connection setting is being respected when the connection is created.

  • For folder mapping jobs between Network File System and Microsoft Office 365, child jobs that were created from a source folder that began with a pound sign (#) would fail due to a SharePoint exception. This issue has been resolved.

Updating the DryvIQ Platform does not update the Command-line Interface (CLI). If you use the CLI, you should update it when you update to a new version of DryvIQ to ensure the CLI is current. Run the CLI install command to update the CLI.  

  • No labels