- Why do I get a "REQUEST_LIMIT_EXCEEDED" error when viewing some macros?
- How do I reduce the number of API calls?
- Is there any form of caching of data in the plugin?
- I try to use =, =eq:, =ne:, =not equals:, =lk:, =like query conditions for data type other than string (i.e. double, int, date, currency & boolean) but all I got is error.
Why do I get a "REQUEST_LIMIT_EXCEEDED" error when viewing some macros?
This error relates to the limit of API calls available in SalesForce.com in any given day, once this limit is reached, no more API calls can be used, so when the plugin tries to fetch data from SalesForce.com this error occurs.
Please refer to the following table for the API call limit for each of the SalesForce.com License types.
| Salesforce.com Edition | API Calls Per License Type | Minimum | Maximum |
|---|---|---|---|
| Developer Edition | N/A | 5,000 | 5,000 |
| Force.com Free Edition |
|
5,000 | 1,000,000 |
|
|
5,000 | 1,000,000 |
| Unlimited Edition |
|
5,000 | 5,000,000 |
| Sandbox | N/A | N/A | 5,000,000 |
Please refer to the How do I reduce the number of API calls? section for more details on how to reduce the number of call to prevent this error.
How do I reduce the number of API calls?
The plugin has a build in cache which caches the SalesForce.com API calls (for more details on the cache implementation and how to fine tune it, please refer to Is there any form of caching of data in the plugin?).
You can further reduce the calls by using broader search queries and then filtering them down using the {xxx-filter} macros (part of Reporting Plugin) to filter down the result set, likewise you can also do your sorting using {xxx-sort} macros (part of Reporting Plugin) to sort your results.
Is there any form of caching of data in the plugin?
Yes, there is, the plugin uses Confluence's caching implementation (Ehcache).
I try to use =, =eq:, =ne:, =not equals:, =lk:, =like query conditions for data type other than string (i.e. double, int, date, currency & boolean) but all I got is error.
We have this issue since earlier version. We might fix this in the next release. It is not included in this release as our main objective is compatibility with Confluence 4 only. Kindly please submit your feature request in our Greenhouse JIRA if you need this feature.
