Overview
Info message indicates that Copy File Action has successfully completed its operations; however, in fact nothing has been copied.
Cause
The message is shown when file masks and wildcards are used to configure Action for processing multiple files and there are no files with names that match specified file mask.
In some cases, attribute or file time filters can screen out every file, meaning the Action has no matching files to process.
Another common reason is that the Overwrite existing files option is disabled, and the destination folder already contains files with the same names. In such cases, Automation Workshop skips copying to avoid overwriting existing content—resulting in zero files being copied even though matching files were found.
Resilience
There are two scenarios where the "0 files copied" informational event may appear. First, when the Resilient file handling option is enabled, the Action proceeds without treating the absence of matching files as an error. Instead of logging an error like "0 files affected", it logs an informational event: "0 files copied", and the workflow continues.
Second, this event may also appear if the error code E104 "0 files affected" has been manually unchecked in the Advanced fallback options. In this case, the Action does not treat the absence of matching files as a failure, allowing the Task to continue and logging "0 files copied" as informational output.
Ask for more…
If you have any questions, please do not hesitate to contact our support team.