Missing Folders on Remote Mounts

A folder removed or moved directly on remote storage can leave Files.com configuration pointing at its former path. Files.com defers cleanup of that configuration so a temporary absence does not immediately remove permissions, Folder Settings, Notifications, or other objects associated with the path.

This preserves configuration, rather than a copy of the missing file contents. It does not restore a remote folder or keep its files available during an outage. Recovery of the contents depends on the remote system.

Configuration During Remote Absence

A missing result from a remote lookup is not enough to distinguish a permanent deletion from a temporary problem. Files.com retains the associated metadata and checks the path again during a 72-hour validation window. If the item reappears, its existing permissions and settings remain in place.

For an unavailable folder, first check its location and the connection account's access on the remote system. A renamed folder can exist at a new path without restoring the original path. Broader credentials do not bring back files that were actually removed.

Confirmed Removals

If the path remains missing across validation, Files.com removes the associated metadata and configuration as it does for a deletion performed through Files.com. Do not rely on a remote-side deletion as an immediate way to remove Files.com access rules or workflows; manage those configurations directly when ending their use.

Folders deleted through Files.com are handled immediately, including removal of their associated configuration. Folder Settings Within Remote Server Mount explains this lifecycle alongside the rules for activity discovered by the Remote Metadata Index.