Delays To Batch and Scheduled Operations

Incident Report for Files.com

Resolved

We have resolved an incident causing delays to batch and scheduled operations on customer sites. Operations that were delayed included scheduled and ad-hoc syncs, moves, copies, automations, webhooks, batch deletes, email delivery, previews, and similar batch operations. This incident occurred between 14:59 and 15:40 UTC.

The proximate cause of the delay was an internal DNS issue in connecting to an internal database. We will share more about the root cause as part of a post mortem.

Due to the database connection errors, and due to a separate logic bug in our logging code, during this time period, a portion of History log entries were dropped from our logs and not saved.

There are many types of logs on Files.com. History logs are the ones found in the web interface under the History tab on the File Manager, and at Logs & Reports > File Actions / History. The History logs are the logs that trigger actions like Automations, webhooks, and notifications.

Since some actions were not written to the History logs, Automations, webhooks, and notifications that would have been triggered by those actions did not run.

Other logs, including API, SFTP, and FTP logs were not impacted by this incident, and you can rely on those logs from this time period for audit purposes.

We have already mitigated the logging code bugs to ensure that a future internal database connection outage of this nature will never result in lost log entries. We will write a complete post mortem with further details.
Posted Nov 16, 2026 - 07:00 PST