API Limits in Salesforce

If you're seeing a "REQUEST_LIMIT_EXCEEDED" error in DayBack, this means that the number of API calls in your org is exceeding your 24-hour limit.

The immediate action to take is to reach out to Salesforce. They will usually temporarily increase a customer's API limit until the problem is resolved. In our experience, this usually happens within an hour, so you'll want to get that going with Salesforce ASAP.

Salesforce can also provide more detailed info on the offending client(s). Salesforce users (including us at DayBack) only have access to a basic usage report in Classic, but it doesn't tell us which integration is the culprit.

A few things to know about this error:

• Your rate limit applies to all your org's API calls, not just DayBack's. Unless we have some kind of runaway loop, DayBack isn't capable of busting through these limits on its own (or at least it hasn't yet).
• A runaway loop could be caused by new custom actions being deployed as part of a DayBack customization or by a new feature being deployed in the DayBack core. Unless there has been a change like this, we can not usually address exceeding your limit in DayBack's code: our queries are usually a drop in the bucket compared to other org activity.
• Because this is a 24-hour limit, you'll likely see the error at the same time every day.
• The most common cause we see here is a flow being triggered with very broad entry conditions. (You should always use entry conditions in your flows, and not just run a flow on all records of an object type. If you have conditions, you can check on the triggering record; do that first.)