Transfer ends in status INTERRUPTED when file does not exist
When the gateway tries to send a file to a remote partner as a client, if the file does not exist on the disk, then the transfer ends in the INTERRUPTED status instead of the expected ERROR status. The error is properly logged, but it is missing from the database transfer entry.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information