The Run Sync automation is used to trigger one or more Remote Server Syncs that have already been configured in your site. This automation does not perform a file operation directly. It initiates sync processes between Files.com and external storage locations such as S3, Azure, Google Cloud, or other Remote Servers you’ve linked through Remote Server Sync configurations.

When to Use Run Sync Automation

Use this automation when you want to schedule or remotely trigger the execution of Remote Server Syncs. This is helpful when you need to coordinate sync operations as part of broader workflows or data pipelines. Instead of relying on manual triggers or isolated schedules set within each individual sync, Run Sync allows you to manage timing and coordination from a central automation. This automation is best used when timing or external triggering of syncs is required, rather than manual execution from the Remote Server Sync page.

It’s especially useful when syncing multiple external locations on a shared cadence. For example, pulling data from several regional storage buckets every Monday at 5PM, or pushing updated content to multiple partners after a batch process completes. This automation can also be triggered via incoming webhooks, allowing it to be connected to external systems or CI/CD pipelines for dynamic control.

Sync Execution Order

Within a single Run Sync automation, you can select multiple Remote Server Syncs to trigger. Each selected sync will be initiated when the automation runs. The order in which the selected syncs execute is not guaranteed, and they run independently of one another.

Controlling How Run Sync Automations Are Executed

Run Sync automations triggered by file actions or webhooks can run in parallel if multiple events occur close together. This is the default behavior for non-scheduled automations and helps improve performance in high-frequency environments.

If you want each automation run to wait until the previous one finishes, you can enable the Always Serialize Jobs setting. This forces Run Sync jobs to execute one at a time. It helps prevent race conditions or conflicts, especially when syncing with remote mounts that do not support overlapping operations.

Automation Run Status

The Run Sync automation records that the sync was initiated but does not wait for the syncs to finish. This means the success or failure of the sync process does not affect the outcome of the automation itself. Even if a sync fails, the automation will still show a successful run since it only tracks whether the sync was started.