New Features and Enhancements

• Unsupported Google Sheets Function Detection: When migrating from Google, DryvIQ now identifies Google Sheets functions that aren't compatible with Microsoft Excel and logs them during export. This means you'll get a clear report of any functions that may be lost, so there are no surprises when you open the exported file.

• Box Connector Permission Check Optimization: When migrating from Box, DryvIQ now skips the collaborations API call for items that don't have unique permissions. This means faster migrations with fewer unnecessary API calls, reducing the chance of hitting rate limits during large transfers.

Fixes

• Updated the Microsoft Office 365 (SharePoint) connector to prevent the incorrect time zone from being used when preserving timestamps using non-batch uploads.

• Resolved a failure to recover during some version retention uploads.

• Fixed an issue where jobs scheduled with specific minutes were running on the hour instead.

• Addressed a case where a canceled batch could lead to multiple items in the tracking database.

New Features and Enhancements

• Enhanced User Mappings Export: The User Mappings export now includes a Job Name column that displays the job name as it appears in the UI, so you can quickly identify which jobs produced each mapping and streamline troubleshooting and reporting.

• Enhanced File Handling for Google Drive Migrations: Migrations from Google Drive and Google Shared Drives now include improved reporting and more accurate file naming. The Processing Overview identifies Google-native files converted to Microsoft Office formats (Native Export) and files with adjusted extensions (Extension Corrected), with filtering available in both simulation and transfer runs. Additionally, files with unrecognized file types now retain their original names and extensions, preventing unintended .bin extensions from being added at the destination. Learn more here.

• Improved Links Export: Link CSV export for migration jobs now includes the complete path in the source_path and destination_path columns, giving you full visibility into where links originate and where they're mapped.

• Faster Permission Retrieval for Google Shared Drive Migrations: Permissions lookups during Google Shared Drive migrations now leverage caching and parent-level permission checks to eliminate redundant API calls. This results in faster migration times, particularly for large folder structures with inherited permissions.

Fixes

• Resolved an issue where migration jobs using Office 365 as a source could become stuck and unresponsive, requiring a service restart to resume.

• Corrected an issue that overwrote running jobs' status to idle, preventing running jobs from displaying properly when filtering.

• Updated link detection and remediation to handle Excel files containing links with paths longer than 255 characters and to filter out false "decoy" link entries that Excel generates internally for long-path references, eliminating noise from link reports.

• Fixed an issue where SharePoint migration jobs failed during batch status checks when using a tenant-level Office 365 connection as the destination.

• Corrected a permissions mapping issue when migrating from Google Shared Drives to Office 365 that could apply incorrect permission levels, resulting in mismatched permissions.

• Prevented root-level folder mappings from being re-created on each parent job run.

• Resolved an issue where NFS/SMB to SharePoint migrations failed with a "Value cannot be null" error when the destination Office 365 user mapping included disabled users missing an email address, ensuring author preservation and permissions transfers handle disabled users in various states without errors.

• Corrected an issue where files with a % character in their name threw an "item cannot be located" error during NFS/SMB to SharePoint migrations.

• Resolved an issue with the Egnyte connector where HTML error responses were not treated as rate-limit responses, causing Egnyte migrations to fail instead of retrying automatically.

• Corrected an issue where files could throw an "item could not be located" error during SharePoint Migration API transfers. The connector now falls back to path-based resolution when an error occurs, improving reliability of file migrations.

• Resolved an issue where "Tracking Information Disconnected/Multiple matches found" errors could occur during Network File System to Office 365 migrations.

New Features and Enhancements

• Timestamp Preservation When NFS/SMB Is the Destination: DryvIQ now supports preserving the last-accessed timestamp when NFS/SMB is configured as the migration destination. This ensures greater consistency with source metadata during migrations. Learn more here.

• New Migrate Report Search: A Search bar has been added to the Reports page, enabling you to quickly locate specific migration reports when working with a large report list. Learn more here.

• Autoscrolling Job Category List in Job Creation Wizard: Improved the Job category dropdown in the job creation wizard with autoscrolling, enabling you to view and select from the full list of available categories during job setup.

Fixes

• Updated job handling to treat “multiple matches found” errors as fatal, setting the job status to Failed so issues are visible without reviewing logs.

• Improved SharePoint Migration API batch response processing to prevent “multiple matches found” errors and increase overall resilience.

• Resolved link remediation behavior causing repeated retries when files were removed from the source, resulting in an “item could not be located” error.

• Restored expected handling of invalid SID warnings so files are transferred successfully while still being flagged for review.

• Updated the Microsoft Office 365 connector to resolve an issue where the error “the given key '1' was not present in the dictionary” occurred during jobs using author preservation.

New Features and Enhancements

• Export Limits Increased: The default export limit for Content and Account exports has been increased to 1 million rows. Organizations can now extract larger datasets in a single operation, reducing the need for multiple exports and improving efficiency when analyzing and reporting on content at scale. This increase is applied automatically, and no user action is required.

• URL-Based Job Status Filtering: Users can now filter by job status directly in the URL (e.g., aspect.execution.job_status=running), enabling faster access to relevant job views and improving usability.

• Ownership Preservation When NFS Is the Destination: DryvIQ now supports ownership preservation when NFS (SMB) is configured as the migration destination. When enabled, DryvIQ applies the source item’s CreatedBy value as the Owner on the destination NFS share. This helps maintain file ownership continuity during migrations to NFS, improving audit and compliance accuracy and post-migration access validation. Learn more here.

Fixes

• Updated the Microsoft Office 365 and OneDrive for Business connectors to support Domain Groups, which were previously filtered out.

• Adjusted the default job status check interval for SharePoint migration jobs from 1 second to 10 seconds to reduce API throttling and improve performance and reliability.

• Updated the Microsoft Office 365 and OneDrive for Business connectors to correct an issue where large (>1 GB) multi-version files could return an “Accept header cannot be satisfied” error during processing.

• Corrected OneNote migration behavior to convert notebooks into folders.

• Updated OneNote workbook conversion logic to account for files skipped by job filters.

• Corrected an issue where Tenant-Level Connections retrieved content from the root instead of the configured site, ensuring content is scoped according to the defined connection settings.

• Updated the Dropbox connector to replace misleading path/no_write_permission impersonation errors with clearer access failure messaging to improve troubleshooting.

• Corrected an issue where timestamps were not properly applied to destination folders in Azure FS, ensuring accurate metadata preservation.

• Updated the SMB connector to ignore symbolic links (due to SMB limitations) and log a clear audit message, preventing unexpected scan and migration failures.

• Corrected an issue where ShareFile returned 0-byte files, ensuring accurate file retrieval.

• Updated the ShareFile connector to use the download specification instead of URI redirects, improving download reliability and consistency.

• Improved retry processing stability by addressing a ReaderWriterLockSlim disposed object error.

• Updated license refresh behavior to prevent unintended expiration during network interruptions, ensuring licenses remain active unless a valid server response confirms expiration.

Important Fix

• Resolved an issue affecting Microsoft 365 and OneDrive source migrations with versioned files: Microsoft recently introduced an API change that caused migrations to fail with an “Accept header cannot be satisfied” error when Microsoft 365 or OneDrive was used as a source and files contained multiple versions. This release includes a fix that restores reliable migration behavior for these scenarios.

  Customers running migrations from Microsoft 365 or OneDrive that include file version history are strongly encouraged to upgrade.

Additional Fixes

• Fixed an issue that could cause connections to become disconnected in certain path-related scenarios.

New Features and Enhancements

• Important Box Note Embedded Images Information: Due to how Box handles embedded images in Box Notes, DryvIQ cannot include them when converting Box Notes to Microsoft Word documents during migration. When it encounters a Box Note with embedded images, DryvIQ will convert the Box Note to a Word document, but the images are omitted from the output. In these scenarios, DryvIQ records a warning in the job logs to indicate that the Box Note contained images that could not be included in the conversion.

• Updated Handling for Pending and Unknown Items: For each job run, DryvIQ will retry items with a “Pending” or “Unknown” status as if they had been flagged for retry, ensuring proper processing.

• More Reliable Microsoft Connection Authentication: Improved Microsoft connection creation by requiring a fresh sign-in for each new connection, ensuring the correct account, permissions, and tenant are always used and preventing issues caused by cached SSO sessions.

• Configurable Large File Handling for Microsoft Graph Connectors: DryvIQ now supports configurable chunked transfer for large files when using Microsoft Graph connectors. Files larger than the configured size (1 GB by default) are automatically transferred in chunks, improving reliability when working with very large files. Learn more here.

Fixes

• Improved duplicate detection in SharePoint and OneDrive so files with equivalent Unicode characters in their names are correctly identified and reported as duplicates instead of failing.

• Resolved an issue in Azure File systems where copied files could become corrupted, resulting in incorrect file sizes or zero-filled content.

• Corrected a timeout issue in the SharePoint connector when transferring large (>1.5 GB) Microsoft Office file versions with author preservation enabled.

• Addressed an issue where Box Notes that failed conversion were retried and copied as .boxnote files instead of being reprocessed for conversion.

• Enhanced event handling so both file updates and moves are correctly processed when they occur close together.

• Stabilized OneNote processing to prevent errors when migrating content and folder structures to SharePoint destinations.

New Features and Enhancements

• Updated Microsoft Connectors for API Compliance: The Microsoft connectors have been updated to use the GetMigrationJobProgress API, ensuring continued compliance with Microsoft’s supported APIs and improving long-term reliability for migration job tracking.

Fixes

• Updated the client ID for Google Drive – My Drive to resolve a connection issue that previously prevented new connections from being created.

• Fixed the Links export for migration jobs to ensure it includes the Job Path details.

• Resolved an issue where SharePoint links containing “%” characters in the file name were incorrectly marked as ignored during link remediation.

• Fixed an issue where actively running scans were incorrectly overwritten in the catalog with a status of “idle.”

• Fixed an issue in the Microsoft Office 365 connector that caused an operation timeout for file versions larger than 1.5 GB when author preservation is enabled for a job.

• Resolved an issue that caused files to be skipped if they were updated and moved (or moved and updated) because only the last event was propagated.

New Features and Enhancements

• Support for Migrating Root-Level Files in Folder-Mapping Jobs: DryvIQ now includes an Include root folder files option for folder-mapping migration jobs. When enabled, the job automatically creates a child job for any files stored directly at the source root level. This ensures root-level files are migrated with the same filters and settings as the rest of the folder structure, providing greater flexibility and consistency when working with directories that contain top-level files. Learn more here.

Fixes

• Fixed the version number displayed on the Licensing and About pages so both now clearly show the correct version.

• Fixed the Search field on the Links tab in migration job reports so it correctly searches the Detected Links column.

• Updated the support link shown in error messages to ensure it provides the correct information for contacting DryvIQ Support.

• Fixed a bug in the NFS connector that caused restoring the last access time to apply Temporary and System attributes to Windows NFS shares.

• Improved OneNote handling so DryvIQ now correctly converts OneNote items during SharePoint migrations when batch mode is enabled.

• Fixed an issue with token expiration in the Google connectors to ensure authentication remains stable throughout migration and scan operations.

New Features and Enhancements

• Renamed Google connectors: DryvIQ renamed its three Google connectors to better align with its connection methodology.

  • Google Drive is now Google Drive - My Drive.

  • Google Shared Drives is now Google Drive - Shared Drives.

  • Google Workspace is now Google Workspace (Service Account).

• Google Connector XLSM Update: Downloading and reuploading Microsoft Excel files or creating them with non-Microsoft applications causes Google to report XLSM files as Microsoft Excel files. DryvIQ previously appended the proper Microsoft Excel extension (XLSX) to the file based on Google’s reporting, so the DryvIQ Google connectors have been updated to no longer add an extension when Google reports an incorrect MIME type for an XLSM file.

• Amazon Chunk Size Configuration: A new configuration option for Amazon allows you to specify the upload chunk size to ensure large files can be uploaded without going over Amazon’s chunk upload limit. Learn more here.

• Inspection Policy Updates: The “all” inspection policy has been updated to flag failed filter content as “ignored” rather than “failed” to ensure accurate reporting of failed items.

• Job Search Bar Availability: The job Search bar is now available on the Jobs and Simulations pages, even when no jobs have been created, to provide a consistent user interface experience.

• New Job Status: Jobs that are pending cancellation will have a “Canceling” status until the process is complete.

• New Job Status Warning: DryvIQ will now display a warning when a job is running but hasn't reported a status in over an hour. This will help you identify jobs that may be stuck.

Fixes

• Fixed an access_denied_insufficient_permissions error in the Box connector when applying a collaborator that already existed.

• Fixed an issue that prevented retry items from being included in the job Overview statistics after a hard reset or complete reset was performed on the job.

• Fixed an issue that caused jobs using “uri” in the target path to not include the full URL in remediated links that point to a separate SharePoint site.

• Fixed an issue with the Microsoft Office 365 connector to preserve the original created by and modified by information during rename operations when the job uses author preservation.

New Features and Enhancements

• Microsoft SharePoint Online tenant connection improvements: DryvIQ now supports using forward slashes (/) when defining the target path for a SharePoint site when creating a job, so you no longer need to use the “%252F” in place of the forward slashes.

• Additional link remediation types for Box: DryvIQ remediates shared file links, shared folder links, and direct download links for Box.

• Content scans support for Unix User and Group accounts: When using the My Computer connection for a content scan, DryvIQ will populate the Owner, User, and Group fields with the corresponding Unix permissions on an NFS share. Note that the SKYSYNC_ENABLE_LOCAL_FILE_SYSTEM environment variable must be set to true to enable the My Computer connection, which is required to connect to Unix in a Linux environment. DryvIQ will update the fields as follows:

  • The Created by/Owner property will get updated with the Owner Unix permission field.

  • The Group Unix permission field will get added to “Group Accounts.”

  • The Others Unix permission field will get added to “Group Accounts.”

Fixes

• Fixed the refine pills for age operators to prevent the display from flipping the greater than and less than symbols (< and >).

• Fixed an issue preventing a content scan policy from being deleted if no scan locations are referencing it.

• Fixed an issue that caused jobs with a qualified path name exceeding 1000 characters not to run.

• Fixed an issue with logging the body of an API request when the Dropbox API returns a “Conflict” error when a user cannot be resolved.

• Fixed calls to the Box API to ensure DryvIQ reads the “Retry-After” header and waits the specified number of seconds between requests when being rate-limited by Box.

• Fixed an issue causing a Microsoft Office 365 connection to become disabled when multiple jobs are queued to run against it.

New Features and Enhancements

• New Flagged Status in File Properties: DryvIQ now tracks and identifies flagged files for content scans. If an error or exception occurs during a content scan, DryvIQ will retain any information it was able to collect before the error and write it to the catalog. DryvIQ will then set the Flagged property. A new Flagged column is available in the File Properties category of the Content grid so you can identify any flagged files. It shows a green check mark for flagged files and a dash for non-flagged files. (If you don’t see this column, click the Edit columns button and verify that “Flagged” under Filter Properties is set as visible.) You can refine the Content list based on this property, and you can use this property in advanced filtering.

  Note the following behavior based on the scan type and scan configurations:

  • For File Inventory scans, DryvIQ records the flagged files in the PolicyItems table (RequiresRetry), allowing delta scans to retry scanning the files.

  • For document set scans, DryvIQ only updates the catalog, so you will need to reset the scan to reprocess items.

  • For archive file types (ZIP, etc.), DryvIQ will flag the main archive file if any of the subfiles in the archive are flagged. (Note that archive file type scanning is only available in DryvIQ Platform version 6.0 and later.)

• Reset Options Moved to the More Actions Menu: The scan reset functionality has been moved to the More Actions menu (ellipses) to make it easier to reset a scan and to make the functionality available for child scans, too. To reset a scan, click the ellipses at the end of the row and select Reset scan from the menu. The reset functionality was removed from the Edit Categories modal as part of this enhancement.

Fixes

• User and group accounts that can’t be resolved are displayed as “Unresolved” on the User Mapping tab.

• The byte sizes for SharePoint and ShareFile folders will now be reported as 0 Bytes to prevent inflated content scan size values.

• The ShareFile Shared Folders connector was updated to fix an upload issue causing an “Object reference not set to an instance of an object" error.

• DryvIQ will skip adding the “Anyone” shared link type if the site does not support anonymous sharing.

• An update was made to the Microsoft CSOM query used for tenant connections to fix “The object specified does not belong to a list” errors during migrations.

• When transferring from Box to Microsoft, Box "Previewer" permissions will be assigned "Can't Download" in SharePoint. Note that the “use_csom_for_permissions": true configuration is required for these permissions to be applied.

New Features and Enhancements

• Content scans now record permissions for the source root, providing more comprehensive reporting about your user and group permissions.

• The “Owners” group for a SharePoint site/library now persists in migration jobs.

Fixes

• An offset was added to the Accounts page export feature to ensure proper export of the items.

• A fix was made to prevent a cast exception when sending migration job notifications.

• The Box connectors no longer sanitize leading spaces in file and folder names.

• Updates were made to the Autodesk BIM360 connector to use the latest Autodesk authentication.

• An update was made to fix a change in Microsoft .NET 8.0 that caused exports not to work in DryvIQ Platform version 5.9.7.

• A fix was made to ensure link remediation respects the “Preserve Most Recently Modified” conflict policy when set for a migration job. When a file is updated on the destination outside of a migration job, DryvIQ will no longer overwrite it as part of link remediation. DryvIQ will flag the file as ignored instead.

New Features and Enhancements

• Microsoft Outlook Exchange connector updates:

  • The Microsoft Outlook Exchange connector was updated to add delete operations.

  • The number of requests per second for the connector was lowered to prevent throttling.

Fixes

• The following updates were made to fix inconsistencies with scan statuses.

  • Scans that aren’t running will have a status of “Idle” instead of “Completed.”

  • New scans that have not yet run will have a status of “Idle - No scan” to help identify scans that have not yet run. These scans will be returned when filtering the scan list for scans with an “Idle” status after the upgrade to version 5.9.7. Existing scans will not be affected by this fix and may not display when filtering the list for idle scans.

  • Scans that have successfully met their stop policy will have a status of “Completed.” Running a scan with a “Completed” status resets the scan’s stop policy.

• When starting a large number of scans, the total number of scans that were started is displayed rather than the total number of scans.

• DryvIQ Regex entity types using the \b boundary have been updated to utilize a more comprehensive boundary, enhancing identification when using OCR for document scans.

• Impersonation is now working for the Dropbox for Business Team Folders connector.

• When OneNote folders are converted in a migration, the item status will now be “Revised” to reflect that the conversion was completed.

• Updates were made to migration jobs to improve handling of HTTP responses for text/HTML content.

• If an exception triggers a retry, the exception information will now be logged for migration jobs using author preservation with the skip_preserve_owners_on_failure parameter set to TRUE.

New Features and Enhancements

Connections

• Google Cloud Storage Connector: DryvIQ now offers a Google Cloud Storage connector for analyzing content in your Google Cloud Storage account. Learn more here.

Settings

• OCR Settings: A new Optical Character Recognition (OCR) setting lets you enable or disable OCR for the DryvIQ Platform. OCR allows DryvIQ to extract text from images and PDF files. Learn more here.

Fixes

Connections

• A null reference exception was addressed for the Amazon S3 connector that caused upload failures.

• Google Shared Drive connections with domain access no longer create duplicate root folders when content scans start from a schedule.

• The Google Workspace and Google Drive connectors were updated to ensure changes to files in the drive root are detected.

• Updates were made to the Google connectors to properly sanitize forward slashes (/) in folder names, ensuring path depth is recorded properly.

• Custom metadata from a Microsoft Exchange connection now displays the property name rather than a GUID.

• Updates were made to prevent a “batch cannot be committed twice” exception error when using the SharePoint Migration batch API.

• SharePoint Libraries are created when authorship/ownership preservation for the destination root folder is enabled.

• Updates addressed an issue with Windows NFS shares that prevented permission propagation when permissions were inherited from the “Parent Object.”

• Currency and numeric custom metadata in SharePoint no longer causes a double conversion error.

Migrations

• Updates were made to the “add” and “rename” processing in migration jobs to ensure folder renames are captured.

• Sanitized file or folder names will no longer cause duplicated items on the destination and a “tracking information for item…” error.

• Updates were made to folder mapping jobs to ensure the correct generated link remediation paths.

• User and Group maps are correctly populated when creating an exception map using the DryvIQ REST API.

New Features and Enhancements

Entity Types

• New Length Exceeds Entity Type: DryvIQ added a new transform entity type you can use to identify paths that exceed a set value. You can only create the entity type through the DryvIQ REST API. Learn more here.

Migrations

• Dropbox Shared Link Remediation: DryvIQ now supports remediating shared links when Dropbox is the source connection. Shared links must be in the supported format, and even then, various scenarios may interfere with DryvIQ’s ability to remediate the shared link. Learn more about remediating Dropbox shared links here.

Fixes

Connections

• The Google connectors were updated to fix an issue that prevented users with commenter access from getting the latest file version.

• Updates were made to the Google connectors to prevent a “The request message was already sent. Cannot send the same request message multiple times” error if DryvIQ encounters rate limits when retrieving versions.

• A fix was made to the Box connector to ensure downloading locked files presents an “item locked” exception rather than an “access denied” exception.

• The Microsoft connectors were updated to change how DryvIQ handles OneNote folders containing non-OneNote files. On the initial transfer to Microsoft 365, DryvIQ will convert valid OneNote folders (as defined by Microsoft) to OneNote files. However, it will not convert OneNote folders that contain non-OneNote files. Instead, DryvIQ leaves these folders as is and transfers them as regular folders.

• File owners are now transferred when migrating from Citrix ShareFile to Microsoft 365.

Migrations

• Items in retry no longer result in a duplicate rename, resulting in additional items appearing in the Items table.

• When processing an “item already exists” response from the migration batch API, DryvIQ no longer performs a size (bytes) comparison to prevent false negatives when determining if DryvIQ needs to transfer an existing item.

Scans

• Updates were made to the Access and Sharing entity type to ensure all item groups display.

• All items are no longer reprocessed on subsequent scans when the File Active User Status entity type is included.

• Tabular format detection has been fixed.

New Features and Enhancements

Migrations

• Link remediation now supports updating links for Dropbox. Learn more here.

Fixes

Discover

• An update was made to fix an issue that caused an error when scanning a document set on a Box folder with the Access and Sharing category enabled.

Migrate

• Statistics are rebuilt when a job is cancelled or when items are in a Retry/Flagged status to ensure the job statistics are correct.

• Items with a revision reason of “Owner preservation failed” will properly display a status of “Revised.” This fix applies to items transferred after the 5.9.4 update and will not affect existing items that have "Owner preservation failed" with a status of “Success.”

• Updates were made to prevent unnecessary API calls during change detection.

• The expired client secret for the Microsoft Exchange connector has been updated.

• The Google Shared Drives connector was updated to ensure the item owner field is available.

• Updates were made to jobs to ensure the “ignore items deleted” setting is respected when enabled for a job.

• The SharePoint Online connectors were updated to retry retrieving versions when the latest version was deleted.

New Features and Enhancements

Migrate

• Improved Character Sanitation: The Dropbox, Box, and Egnyte connectors were updated to replace emoji characters with underscores in file and folder names for platforms that do not support these characters.

• New Filter Reason Column Option: The Job Items page now has a “Filter Reason” option when customizing columns. When selected, this column displays why the item was ignored in the job. This field will also be included in the Items export. Learn more here.

Settings

• New SSL/TLS Server Setting: The SMTP Server setup now allows you to specify the SSL/TLS support you want to use for the server. Learn more here.

Fixes

Connectors

• Updates were made to fix an issue that prevented file transfer to Dropbox personal accounts.

Migrate

• Kerberos support for SMB file shares has been restored.

• Updates were made to prevent the rare occurrence of duplicate folders on the destination when an IOException is thrown.

• The Google Drive, Google Workspace, and Google Shared Drive Connectors were updated to ensure files without extensions get extensions added based on their MIME type.

• Updates were made to prevent API calls from failing if they did not include a sort parameter.

• The Network File System connector was updated to display a more useful message when failing to resolve a user in a Windows environment. This scenario will produce the following message: "Security Identifier could not be resolved: <windows exception message>."

• Using the Box folder ID rather than the path no longer produces an error when scripting jobs.

Settings

• Categories now populate on the Add Recipient modal in the Notifications setup.

New Features and Enhancements

Discover

• Item scan count added back to scan status: The item scan count has been added back to the information for running scans to help you track the scan progress.

Migrate

• New SharePoint Online configuration option for permissions: For Microsoft SharePoint connections, a new use_csom_for_permissions configuration option was added to specify that you want to use the CSOM API rather than the Graph API for retrieving and setting permissions. This setting is useful if you want to maintain “can’t download” permissions since the Graph API has limitations on what permissions it provides. Learn more here.

• Set inspection policy during job creation: You can now set the Item Inspection Policy when creating a job. A new Change item inspection policy setting has been added to the Behaviors page in the job wizard. With the toggle off, the default inspection policy will be None. Enabling the toggle allows you to set the policy to Filtered, Shared, or All. Learn more here.

Connections

• Dropbox connector improvement for rate limits: Improvements were made to the Dropbox, Dropbox for Business, and Dropbox for Business Team Folders connectors to limit the number of requests for shared links, which should reduce rate limiting.

Fixes

Migrate

• Updates were made to ensure file names are truncated or a sanitization exception is added to the activity based on the job settings if an item name exceeds the destination’s limit on a rename operation.

• The last_failure_message column in the jobs export now populates for all jobs (where applicable).

• Versions now transfer from SharePoint on-premises connections.

• The Link Detection feature was updated to handle “null exception” and “set attribute” errors during link remediation.

• DryvIQ will no longer transfer items if they have been added to or moved to a subfolder excluded by job filters.

• A fix was made to ensure items in retry are properly flagged with a “retry” status and not marked as “completed.”

• Updates were made to fix list items in Box Notes not converting during migration.

Govern

•  The Microsoft Information Protection (MIP) Classifier Extension was updated to preserve timestamps when updating a file with an MIP label.

Connections