Skip to main content

Asynchronous (Backgrounded) Operations

Large or complex operations on files are sometimes performed asynchronously. Examples include copying files, moving files from Files Native Storage to a Remote Server, moving files on or between Remote Servers, renaming files or folders on Remote Servers, and deleting folders on Remote Servers. Any copy, move, or delete operation can potentially run asynchronously. We are constantly optimizing our platform and its services, so the set of operations that can run asynchronously is always evolving.

Asynchronous operations improve performance and make features on remote mounts behave similarly to locally attached storage.

An asynchronous operation can be triggered from any connection type, including the web portal, any protocol connection (FTP, SFTP, etc.), the REST APIs, and our SDKs.

Web Portal

When you start one of these operations, a Processing message confirms that it is running in the background. When a request is being processed in the background, status information appears in the web portal UI under a dropdown labeled Actions In Progress. If an operation remains in Actions In Progress for an unexpectedly long time, contact Files.com support. If you triggered the operation through the REST API or an SDK, include the FileMigration IDExternal LinkThis link leads to an external website and will open in a new tab from the API response so support can investigate the specific operation.

API

Asynchronous operations triggered through the REST APIs return a FileMigration IDExternal LinkThis link leads to an external website and will open in a new tab in the API response, which can be queried for the status of the migration operation.

SDK

Some of our SDKs manage the asynchronous operation and present it as a synchronous operation. We are extending this capability to all our SDKs, including those used by our iPaaS partner connectors.

Desktop Apps

The Files.com Desktop app, Mobile app, and third-party client apps are unaware of asynchronous background operations and reflect the current view of files and folders. Once the asynchronous operations complete, refreshing reflects the updated file and folder view.

Sessions

The results of an asynchronous background operation may be reflected differently between user sessions. For example, the user session that initiated the operation reflects the outcome before other user sessions do.