A Login Rate is the number of times a user attempts to log in to Salesforce within a given period of time.
Login Rate Limiting allows Salesforce to limit the number of login requests on a per-user basis to avoid performance impact on our services and improve security when logging into Salesforce.
What causes the Login Rate Exceeded error?
Login requests exceeding 3,600 requests per hour per user will be blocked, and the LOGIN_RATE_EXCEEDED error will be captured in the org's Login History.
How should I troubleshoot Login Rate Exceeded errors (see examples)?
We recommend that you monitor and review your orgs API integration users’ Login History to identify any users that may repeatedly generate calls to log in to Salesforce that exceeds the threshold of 3,600 requests per user, per hour.
Note that Login History for requests that exceed the Login Rate Limit are no longer written for every failed attempt. One history row at least will be written for the LOGIN_RATE_EXCEEDED error to aid in troubleshooting. For more information please review Login History Entries Are Reduced When Login Rate Limiting Is Active.
How can I get more information?
If you have further questions or need assistance with identifying the process and user that may be exceeding the login rate limit, please reach out to Support by opening a case via Salesforce Help.
Example #1: Review API integrations that use SOAP
Make sure that you are reusing the session, and not making a login call for every API request. For more information please review our SOAP API Developer Guide.
Example #2: Review of Automated Jobs
Review any automation jobs that are continually logging into Salesforce that may exceed the 3,600 calls per user, per hour limit.
Example #3: Review Integrations using the same common user account
Check that your integration is not using the same common user account to proxy all requests made by end users.
000381578

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.