Skip to main content
Skip table of contents

05/10/22 Ver

Release Notes - [Thru AFT] [Ver]
Release Date: [05/10/22]

[New Features]

  • Transfer Manager and Processing Manager now support a shutdown mode where new transfer requests are blocked. While in shutdown mode the managers will wait until all pending requests complete before terminating the service. This allows deployments without a maintenance window.

  • Processing functionality has removed from the Transfer Manager and placed into a new micro service: ‘Processing Manager’. This allows independent scaling of the file transfer and file processing services

  • Processing on source flow endpoints serviced by a Node always runs on Node before uploading to the cloud

  • Thru Node Installer script supports legacy Windows Server 2012

  • Activity Page has new filter by file transfers that were quarantined by Antivirus.

  • Antivirus scans files of unlimited file sizes.

  • Flows trigger UI and Email alerts when virus files are detected.


  • Improved performance and scalability of the back-end

  • Activity page has changed to facilitate better performance. The page will now automatically load results as you scroll instead of frontloading all results.

[Other Notes]

  • Antivirus is now enabled for all endpoint types except Node.

  • Node Retention is no longer required as all temporary files are immediately removed.

  • Improved the visibility for org users on activity page for files that transfer between organizations.


The information in this document is subject to change without notice. This document is intended for the use of Thru Inc. staff, Thru Inc. customers or persons having signed an NDA with Thru Inc. for the purpose of the agreement under which the document has been submitted. No part of this document may be reproduced or transmitted in any form or means without the prior written permission of Thru Inc. The document has been written to be used by professional and properly trained personnel and the reader assumes full responsibility when using it. Thru Inc. welcomes readers’ comments as part of the process of continuous development and improvement of the documentation. Thru Inc. liability for any errors in the document is limited to the documentary correction of errors. Thru Inc. will not be responsible in any event for errors in this document or for any damages, incidental or consequential (including monetary loss), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to applicable laws.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.