Destination Exists

When an Automation moves or copies a file and a file or folder already exists at the destination path, Files.com does not replace it. What happens to the run then depends on the Automation type.

A Move Automation records a failure against that file, with the message "The destination exists."

A Copy Automation records the file as skipped, with the message "already exists on destination", and the run itself completes successfully. A Copy Automation that appears to have worked can therefore leave the destination file untouched.

When replacing the file is what you want, turn on overwriting for the Automation.

One cause to check is a second Automation configured with the same destination folder. Check the destination paths in all automation workflows.

When the automation is triggered by file actions or webhooks and multiple runs start close together, the runs can overlap and cause file conflicts. To avoid this, enable the Always Serialize Jobs setting, which forces runs to execute one at a time and prevents overlapping writes.

An existing destination file can also indicate that a race condition caused another process to create the file first.