Rate Limit

Summary

Baselines for Confluence app employs Rate Limiting to avoid the overuse of the service.

Rate Limits control the number of reports that you can get from the Baselines service in a predefined time period. This includes all report requests ...

Main reporting screen
Dashboard gadgets
Issue view screen tabs
REST API
File exports

Baselines prepares its reports based on data from Jira Cloud. Sending very frequent report requests puts too much pressure on both the Baselines service and your Jira Cloud instance. Rate limits are put in place to protect the performance of both the Baselines service and your Jira Cloud instance.

What are the limits?

The exact limits are not public because limit definitions are ever-changing. We are continually monitoring, improving, and fine-tuning the system for better performance.

Limits are set well above the average use so customers should not expect to hit rate limits under daily use of the app. Limits come into play, especially for REST integration scenarios where an unrestrained number of requests are sent in a very short time period.

What happens when you hit the limit?

When you hit the rate limit, your requests will return HTTP 429 with a response like...

CODE

Baselines for Confluence rate-limit exceeded.
You have sent too many requests in a short time period.
See the following document for details about rate-limit: 
https://dev.obss.com.tr/confluence/display/MD/BSL+Cloud+-+Rate+Limit

Further Support

If you are hitting rate limits unexpectedly and the guidance in this document is not enough for you, please reach our support team as instructed here.