Jira limits how many requests an app can make in a short period of time, to protect performance across your site. If your Jira site is very active or your analysis scope is large, Elements Pulse's first-run analysis may occasionally hit this limit.
Why this happens
Saving an Analysis Scope triggers Pulse's first-run analysis, which imports and processes up to 12 months of historical data for your selected segment. Depending on your site's activity and the size of your scope, this can involve a large number of requests to Jira in a short time.
What this means for you
If this happens, Elements Pulse lets you know that your analysis is taking a bit longer than usual.
-
No data is lost. Elements Pulse automatically resumes once Jira's rate limit clears.
-
No action is needed on your end. You don't need to retry, refresh, or reconfigure anything.
-
This only affects first-run analysis. Day-to-day use of your dashboards isn't impacted, since your data is pre-computed and stored rather than queried from Jira live each time you open a dashboard.