Overlapping Workflows (v1)

If overlapping jobs produce a missing source, an unexpected replacement, or incomplete output, compare their run times, selected files, and file activity for the affected path. Include activity from Syncs, users, and applications working directly on a Remote Server. Jobs sharing a folder are not, by themselves, evidence of a conflict. The workflow coordination guide explains the dependencies to account for when configuring them.

A Source Is Moved Before Another Job Reads It

For a "not found" error, check whether another operation moved or deleted the source between selection and processing. If the file was not selected at all, check whether it had already left the source folder before the run listed that folder. Compare the move or deletion time with the affected run, and check any Sync configured to delete source files after transfer.

When that sequence confirms the conflict, change the workflow so every required copy succeeds before the source is removed. Follow the shared-source example for ordered distribution. A "not found" error without the corresponding file activity does not establish that another job caused it.

Two Jobs Write the Same Destination Name

For a destination already exists result or an unexpected file at the destination, compare the resolved destination paths and overwrite settings of the jobs involved. Check which run or user last wrote the path. A file already present before either run started can produce an existing-destination result without any overlap between jobs.

If independent outputs are resolving to the same path, give them distinct names or folders. If one output is intended to replace another, arrange the work in completion order. Turning on overwriting alone does not determine which output should be retained.

A Producer Is Still Writing the Source

For an incomplete output, compare the source application's transfer or save status with the Automation's read time. Check the source's completed size and contents against the file delivered. A remote application or an incremental WebDAV upload may have exposed the file before writing finished; a Remote Server Mount does not provide evidence of that application's completion.

If the Automation began reading too early, configure the producer and consumer to use a completed-file handoff. Verify the complete source and inspect any partial delivery before rerunning the affected operation.

Coordinating Workflows

If overlapping runs belong to the same Automation, check its Always Serialize Jobs setting. If separate Automations or Syncs are involved, enabling that setting on each Automation does not order their work relative to one another. Review their shared paths and dependencies using the primary coordination guidance.

If a file selected for processing has no recorded outcome, or a completed transfer does not contain the expected data and the available activity does not explain it, contact Support with the affected runs and paths. Concurrent work alone does not explain a missing record or establish why the output is incorrect.