MuleSoft Salesforce Connector: Unexpected processing delays caused by Connection Pool exhaustion when concurrent requests exceed Max Entries

Symptom

You see following symtom with using MuleSoft Salesforce Connector:

• Salesforce Connector operations take longer than expected to complete (several seconds to tens of seconds)
• No errors or timeouts are thrown; processing eventually completes successfully
• More likely to occur under high load or during parallel flow execution
• When DEBUG logging is enabled (Ref [1]), the following messages are observed (the time gap between them corresponds to the delay):

Cause

The Salesforce Connector's Connection Pool has a maximum number of simultaneous connections defined by Max Entries (default: 10, Ref[2]). When the number of concurrent requests exceeds this limit, requests are queued until a connection becomes available, resulting in processing delays.