Skip to main content
Feedback

Managed File Transfer Release Notes for July 2026

July 25, 2026

Automated File Transfer v6.13.0.0

New
We added these features

  • Added support for "Password and SSH Key" authentication on Internal SFTP endpoint configurations, so you can secure file transfers with both password and key-based authentication. (AFT-790)

  • Increased the maximum length of the AFT username field to 400 characters so that users with longer email addresses can be created as application users. (AFT-969)

  • Enhanced API logging, capturing additional authentication context such as user ID, username, authentication type, and client details, enabling you to better track user activity, troubleshoot issues, and perform security audits. (AFT-812)

  • Added the endpoint type Boomi MFT Connector in preparation for a new connector coming in a future release. (AFT-656, AFT-439)

    caution

    The current Boomi MFT Connector requires that you use the Thru IPaaS Connector endpoint type.

Fix
We fixed these issues

  • Fixed the file acceptance deduplication for SFTP and FTP source endpoints with Windows drive-letter server paths, preventing the same files from re-transferring on subsequent polls. (AFT-960)

  • Fixed scheduler day-of-week not rolling over correctly on UTC conversion, ensuring schedules fire on the intended local day regardless of time zone offset. (AFT-810)

  • Fixed an issue where bulk resending multiple files to a target flow endpoint fails, enabling you to successfully resend multiple files in one operation. (AFT-819)

    MFT Runtime (Node)

  • Improved LiteDB engine recovery, enabling more robust handling of persistent data corruption by escalating through reopen, rebuild, and recreate steps when initial recovery attempts fail, without requiring a process restart. Enhanced fault isolation by skipping retries for non-recoverable errors and allowing in-memory queue fallback during persist failures, preventing a single issue from stalling an entire transfer request. (AFT-1098)

  • Fixed a crash loop at runtime startup when the node.db file is corrupt, enabling you to recover from database corruption without manual intervention. (AFT-1050)

  • Improved MFT node drain behavior, preventing indefinite hangs and enabling seamless runtime updates by adding a drain timeout, bounding download worker execution, and ensuring accurate in-flight counters. (AFT-951)

  • Fixed LiteDB corruption issues that were blocking cloud uploads on source MFT nodes, preventing disruptions to file delivery for critical shipment files. (AFT-961)

On this Page