Logging and Error Handling for Sync

Files.com records a complete log of every sync action and each sync run, including details about which folders were listed, which files were transferred, and which files were skipped.

You can download the raw logs for processing on your side. Logs are text files where each line of the file is a JSON hash containing the information about a particular log item. Process the log file line by line, running each line through a JSON parser.

We also provide a rich API for querying these logs. This API offers many filtering options.

We are working on the ability to export these logs to external SIEM services for our Enterprise customers. If this is something you would be interested in, please let us know.

When errors are detected in a sync, Files.com automatically alerts site admins via email. You can also use the Sync Logs API to query for failed external events.

To see all Sync Logs across your site, go to the Automated Actions page under Logging in the left navigation in the Web UI.

Files.com retries failures automatically. If a Sync fails, it is logged as an error once all retry attempts have been exhausted. Each scheduled Sync is independent, so one scheduled Sync failing does not prevent the next scheduled Sync from attempting to run.

Site Alert Emails

When a sync operation fails, site admins who have not disabled site alert emails receive an email notification.

The site alert emails may also include other types of important notifications, such as key expirations or problems with SSO. All sync related items appear in a list titled SYNC FAILURES.

If there are multiple failed syncs, all of them appear in the same email. The email includes a link to access the details of each failed sync in the Sync Log along with the time of the failure.