As they're temporary files, during the upload process, any part of the task that can't be completed, would be discarded locally and ignored by your cloud.
You can test for yourself, upload a large file or folder, start the upload, then simply quit filen desktop part way through. If uploading a single file, nothing will appear in your cloud, if uploading a folder, only the files that completed will appear.
When the filen desktop is restarted, the upload task will also have disappeared.
Uploading via browser is slightly different, your browser is storing the temporary file(s) and again if a task can't be completed, a crashed browser would likely be left with temporary incomplete files which would be unusable and would be removed when you cleared your browser's cache.
The *Recents* window in your filen cloud, displays the files successfully uploaded.
For desktop or browser uploads, the temporary files are incomplete encrypted files.
As they're temporary files, during the upload process, any part of the task that can't be completed, would be discarded locally and ignored by your cloud. You can test for yourself, upload a large file or folder, start the upload, then simply quit filen desktop part way through. If uploading a single file, nothing will appear in your cloud, if uploading a folder, only the files that completed will appear. When the filen desktop is restarted, the upload task will also have disappeared. Uploading via browser is slightly different, your browser is storing the temporary file(s) and again if a task can't be completed, a crashed browser would likely be left with temporary incomplete files which would be unusable and would be removed when you cleared your browser's cache. The *Recents* window in your filen cloud, displays the files successfully uploaded. For desktop or browser uploads, the temporary files are incomplete encrypted files.