function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
natemanleynatemanley 

Does high activity through API cause timeouts?

We have done a tone of development that integrates with SF via the .NET Data Provider (found on SourceForge). We currently are using a single user that is our API user...meaning it is a non-human user...soley for the purposes of connecting from integration applications.

This API user sometimes is logging in as frequently as every 1-2 seconds.

Lately we have seen an huge increase in the amount of time out errors from SF:
"The underlying connection was closed: An unexpected error occurred on a send."
"Could not establish secure channel for SSL/TLS"

Is there any reason to think that very frequently logins by the same user trip on themselves? Doesn't really make any sense but wanted ask.

Thanks.
DevAngelDevAngel
Hi natemanly,

No, this shouldn't cause timeouts. It does concern be though that you are logging in so frequently. Why are you not taking adavantage of the two hour (config dependent) session expiration. You should not be logging in any more frequently than once an hour for a two hour sessionl life span.

This causes way too many extraneous calls and increases the chances of getting some kind of communication glitches across the wire.