Connection Limits for Popular Counterparties

A destination used by several Files.com customers can receive many connections from the same shared outbound address. Files.com limits aggregate connections to these destinations so one shared route does not overwhelm the remote service. Your connection can therefore receive less parallel capacity than its configured Max connections value.

This shared-address limit differs from a partner limiting its own account, IP address, or total service capacity. Increasing Max connections does not bypass either kind of limit.

Identifying the Limit

The Outbound Connections log records connection_limited_due_to_popular_counter_party when the shared-route limit prevents a connection. Correlate the affected destination and time with the workflow's failures. That message identifies the platform's aggregate limit; a remote service's own rejection can have a different error.

Capacity becomes available as aggregate use falls. Repeated overlapping runs add demand rather than correcting the cause. Review the combined work using the destination and the connection route before increasing concurrency.

Dedicated Outbound Addresses

We recommend dedicated IP addresses for critical or high-volume partner connections affected by shared-address contention. Configure the Remote Server to use those addresses and give the remote operator every address shown for the selected route.

Dedicated addresses separate your route from other customers' shared-address traffic. They do not increase the remote server's account limit or remove its throttling rules. Coordinate the allowed concurrency with its operator, and contact Files.com Support if the connection continues to encounter the shared-route limit after its routing is corrected.