Continuous improvements

Agile Hive follows Atlassian’s recommendations for handling rate limits and continuously adopts new platform capabilities as they become available.

Reducing the impact of rate limits is an ongoing effort. We continuously optimize Agile Hive to improve performance, reliability, and the handling of rate limits. Follow our Agile Hive Changelog for the latest improvements.

Introduction

Rate limits are a normal part of working with cloud services. This page explains why they occur, how Agile Hive handles them, and what users and administrators can do to reduce their impact.

Why am I seeing this notification?

Open

You may occasionally see a notification informing you that Agile Hive is retrying a request after a rate limit has been reached. This means that Jira Cloud has temporarily rate-limited a request made by Agile Hive.

Agile Hive does not create or enforce these rate limits. Instead, Jira Cloud temporarily instructs applications to wait before sending additional API requests.

The countdown shown in the notification reflects the waiting time returned by Jira Cloud. It is not a delay introduced by Agile Hive.

The notification is intended to make these temporary delays visible. It does not indicate that Agile Hive is intentionally limiting your work.

What are rate limits?

Agile Hive communicates with Jira Cloud through Atlassian’s APIs. To ensure a stable and reliable service for all customers, Jira Cloud limits how many API requests can be processed within a given period.

To keep boards, reports, and calculated values up to date, Agile Hive automatically performs background processing whenever work items change. This background processing helps keep Agile Hive data consistent across boards, reports, widgets, and calculated fields.

Rate limits are more likely to occur after operations that affect a large number of work items, such as creating, updating, or moving many work items. In these situations, Agile Hive processes additional background updates to keep calculated values and reports up to date.

Depending on the type of request, rate limits may apply to:

• a specific user,

• the Agile Hive app, or

• a combination of both.

As a result, one user may encounter rate limits while other users continue working normally.

Learn more about Fields and Reports to understand how Agile Hive calculates and displays this information.

For more information about rate limiting in Jira Cloud, see the Atlassian documentation.

How does Agile Hive handle rate limits?

Agile Hive is designed to handle rate limits automatically.

When Jira Cloud requests a delay, it also specifies how long applications should wait before retrying the request. Agile Hive follows this instruction and automatically retries the request after the specified waiting time.

Retrying immediately would likely result in another rate limit. Waiting for the recommended amount of time helps requests complete successfully while avoiding unnecessary API traffic.

In most cases, the operation continues automatically once the retry is performed. During periods of high background activity, some background updates may take longer to complete because they are processed within the API limits defined by Jira Cloud.

Although automatic retries resolve most situations successfully, some background updates may require multiple retries before they are completed.

Can rate limits be reduced?

Rate limits are defined by Jira Cloud and cannot be disabled by Agile Hive.

However, Jira administrators can reduce the impact of rate limits for background operations by configuring Account Pooling in the API Settings of Agile Hive. Instead of sending all background API requests through a single account, Agile Hive distributes these requests across multiple configured accounts.

This separation of background processing from interactive user requests can improve the responsiveness of Agile Hive while background updates are being processed. It can reduce the likelihood of rate limits, although it cannot eliminate them completely.

Account Pooling requires dedicated user accounts with the appropriate permissions. For configuration requirements and setup instructions, see the API Settings.

What can I do?

In most cases, no action is required.

While Agile Hive is waiting:

• Wait for the automatic retry to complete.

• Avoid refreshing the page.

• Avoid triggering the same action multiple times.

Refreshing the page or repeating actions generates additional API requests and may increase the waiting time.

If a large background operation is currently in progress, waiting for it to complete is usually the fastest way to resolve the situation.

When should I contact support?

Contact Agile Hive Support if:

• requests repeatedly fail even after automatic retries,

• operations remain blocked for an unusually long time,

• background calculations do not complete after waiting for a reasonable amount of time.

• rate limits occur so frequently that they significantly affect your daily work.

Before contacting support, Jira administrators may also want to review their API Settings configuration.

If the issue persists, please contact Agile Hive Support.

If possible, include information about the affected operation, when the issue occurred, and whether it followed a bulk update or automation.