...
When a new snapshot is generated, Jira Snapshots communicates with Jira to retrieve the data. Sometimes it also communicates with 3rd party systems (like Xray) to get data from them. Typically- there will be multiple requests for data. The amount of requests is related to how many issues are included in the Snapshots, and how many levels are configured. For example, A single level Snapshot snapshot which retrieves 100 issues, will require far less requests to Jira then a two level Snapshot with 1000 issues in the first level and another 1000 in the 2nd level.
...
In busy Jira environments, there could be other sources of communications into Jira, which are unrelated to Jira Snapshots. So there could be a situation where Jira throws a 429 Error during a snapshot operation, but that Jira Snapshots is not the sole trigger of the loadburst. In these situations, waiting five or ten minutes may be sufficient to be able to run a succesfull snapshot.
...
Start by attempting again after five or ten minutes.
If a 2nd attempt is not succesfull, then try to narrow down the amount of issues or the number of levels in the request. You are also encouraged to raise a support ticket to with us ( support@radbee.com ). We are constantly working on refining and improving the scalability of Jira Snapshots and we want to hear about your needs in terms of size and complexity of data.
When contacting us (support@radbee.com) about a 429 Error,
...
include this information:
The url of your Confluence site
The tier of your Jira Cloud instance
The number of issues that need to be retrieved in each level of your snapshot