Some remote servers implement rate limits for the number of connections that can be made to them.

These limits are applied by the external systems and not by the Files.com platform.

If you use an Automation, with large quantities of files to a remote server that has rate limits then you may see errors like this in the logs:

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

Files.com will react to these rate limit warnings by slowing down reconnection attempts and reattempting the actions again later.

The rate limit is determined by the remote server and we are unable to know what the limit is until it's reached.

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

Working with a rate limit is somewhat of a science project in that you'll need to try various configurations and permutations to find the ones that work best while not triggering the rate limit throttle.