If your workflow is configured to be triggered based on the file creation and modification and the corresponding file size is zero bytes, automation may fail particularly when you are exchanging files with 3rd party services (example, Azure storage) and an error may not be logged in the Files.com logs.

This occurs because some types of remote server do not support zero byte files.

In this case, check the remote server's documentation about zero byte size files.