Rate Limit Throttling

Some remote servers limit the number of connections that can be made to them. These limits are enforced by the remote system, not by Files.com.

When an Automation moves large quantities of files to a rate-limited remote server, you'll see errors like this in the logs:

Errored while trying to Connect: 'Activity Limit Reached: The request has been throttled'

Files.com reacts to these rate limit warnings by slowing down reconnection attempts and reattempting the actions later. The remote server determines the rate limit, and Files.com has no way to know what that limit is until it's hit.

Check the remote server's throttling settings, activity logs, or connection limit settings to find the threshold.

Tuning around a rate limit is an iterative exercise. Adjust the Automation's configuration — concurrency, file batch size, scheduling — until you find a combination that completes the work without triggering the throttle.