Will MFT Pull Job Retrieve Incomplete Files via SFTP?
This article applies to all MetaDefender MFT Version releases deployed on Window/Linux.
Summary
When performing a PULL action in OPSWAT MFT, the process may sometimes stop unexpectedly. This document explains whether MFT retrieves incomplete files during such transfers.

Use case
During an active MFT job, MFT first verifies and accumulates the file size before initiating the transfer process.
In this test, three file types were used:
light_test
medium_test
heavy_test

Test File Execution
Example: A successful PULL action
- Job Logs: Show standard processing with no interruption
- Processing Status: Completed
- Final Status: Success

JOB logs

Processing status

Final status
Issue – Scenario 1: Job Interrupted
In cases where the job is interrupted or disconnected unexpectedly during execution, the file transfer is aborted.
- Result: No files are received by MFT.
- Error Logs: Indicate termination or connection failure.

Error logs
Issue – Scenario 2: File Still Being Written
When a file is still being written to (e.g., ongoing upload to SFTP), MFT detects it as incomplete or in use.
- Result: MFT will not retrieve the file. Only fully written, unmodified files are pulled.
- Job Logs: Reflect skipped or untransferred files.

JOB logs

In this scenario INCOMPLETE file will not be retrieved. And only unmodified files are pulled to MFT
If you have followed all of the steps above but are still unable to resolve the issue. Please follow these instructions on Creating Support Packages - MetaDefender Managed File Transfer before creating a support case or chatting with our support engineer.