Skip to main content
Feedback

Managed File Transfer Release Notes for January 2026

January 31, 2026

Automated File Transfer v6.8.0.0

New
We added these features

  • Increased the limit of the Amazon S3 endpoint file path to 1024 characters (UK region only). (AFT-177)

  • Modernized MFT Runtime architecture to implement versioned directory structure with graceful migration for existing installations, rollback capabilities, and controlled update mechanisms. The runtime executable is renamed from Thru.MFT.TransferManager to Boomi.MFT.Runtime. Linux runtimes will be updated automatically, but Windows runtimes require a manual update. (AFT-48)

    Old directory structure:

    /opt/node/
    ├── logs/
    ├── TempRepository/
    ├── Thru.MFT.TransferManager  ← Executes directly
    ├── appsettings.json
    ├── NLog.config
    └── node.db

    New directory structure:

    /opt/node/
    ├── logs/
    ├── TempRepository/
    ├── version              (contains: v2025.11.19)
    ├── version_history
    ├── launcher.sh
    ├── appsettings.json
    ├── NLog.config
    ├── node.db
    ├── v2025.11.19/
    │   ├── Boomi.MFT.Runtime  ← Executes
    └── v2024.08.01/
        └── Boomi.MFT.Runtime

    Windows manual update instructions

    You can update Windows runtimes by using the MFT portal or API. These steps must be repeated for each Windows node.

    MFT portal

    1. Log in to the MFT Automated File Transfer portal.

    2. From the Organizations tab, click the associated organization < MFT Nodes and then click the node to update it.

    3. Click Download MFT Node.

    4. Click Copy next to the install command.

    5. Run the command on the machine with the associated node.

    The update process will prompt you for your username and password. Then it will migrate your installation and trigger a graceful restart within 15 minutes.

    API

    Boomi MFT support will provide a list of Windows node IDs and other information per customer.

    1. Use API call https://{region}.thruinc.com/api/ThruNodes/Commands, using the MFT Node Id and platform (win-x64).

    2. Copy the install string received from the first step.

    3. Run on machine with the associated node.

Fix
We fixed these issues
  • Fixed a defect with the MFT runtime automatically treating queued files as failed transfers upon runtime restart.
  • Fixed a defect where flow endpoint schedules were not getting published correctly.
  • Fixed a defect where the MFT runtime would get stuck in an update loop.
On this Page