Skip to main content

Destination Exists

When an Automation moves or copies a file and the file or folder already exists at the destination path, the run fails.

This typically happens when multiple Automations are 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.