General Limits for Salesforce Connect OData Adapters

If your users or applications encounter rate limit errors for OData callouts, try one or more of the following.

• Select High Data Volume in the external data source definition. Doing so bypasses most rate limits, but some special behaviors and limitations apply.
• If you have Apex code that invokes the external system, modify that code to cache frequently accessed external data that seldom changes.
• Contact Salesforce to request a higher limit.

For OData 2.0 and 4.0, an org is limited to:

• 100k new external object record IDs per hour for long-term ID mapping
• 100k new external object record IDs per hour for short-term ID mapping

Starting in the Spring ‘25 release, these limits are removed for OData 4.01. This functionality is available to orgs hosted on Hyperforce on a rolling basis.

Note To view external object records in Lightning Experience, Salesforce Connect maps the external IDs of the record to Salesforce IDs. Mappings classified as short-term refer to records retrieved via Search results only. Mappings classified as long-term refer to records retrieved by all other Lightning Experience components, such as List Views. Record IDs not viewed in 365 days are subject to deletion unless the mappings have customer data attached to them.