Run Sync (v1)
The Run Sync action in Automations v1 triggers one or more 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 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 lets you 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 Sync page.
It is 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.
Permissions and Sync Selection
Site Administrators, Workspace Administrators, and Folder Admins can create a Run Sync Automation in v1. Every selected Sync must belong to the same Workspace as the Automation.
A Folder Admin can select any Sync in that Workspace, including Syncs they cannot view or manage directly. This lets them trigger a configured transfer without managing the Sync's configuration.
Sync Execution Order
Within a single Run Sync automation, you can select multiple Syncs to trigger. Each selected sync is 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
When triggered by file action based triggers or inbound webhooks, Run Sync automations execute jobs in parallel when multiple events occur in close succession. This is the default behavior for non scheduled automations and improves performance in high frequency environments.
To run one Automation job at a time, enable Always Serialize Jobs. This orders the runs of this Automation, each of which initiates its selected Syncs. It does not wait for those Syncs to finish or coordinate them with other workflows. If a later step needs the transferred files, use Sync run results or Sync events to establish completion before starting it.
Automation Run Status
The Run Sync automation records that the sync was initiated but does not wait for the syncs to finish. The success or failure of the sync process does not affect the outcome of the automation itself. Even if a sync fails, the automation still shows a successful run because it only tracks whether the sync was started.