ST-2026-243 · Transition & enforcement
Atlassian rebalances Forge user-led invocation rate limits
Atlassian changed the per-installation user-led invocation limit from 5,000 requests per minute to the first of 300 requests per second or 7,000 requests per minute, while removing the separate 30,000-per-minute environment limit.
Previous state
User-led Forge invocations were limited to 5,000 requests per minute per installation, alongside a 30,000-requests-per-minute environment limit and a 1,200-requests-per-minute per-user limit.
Current state
Each installation may now make user-led invocations until it reaches either 300 requests per second or 7,000 requests per minute, whichever occurs first; the environment-wide 30,000-per-minute limit is removed and the 1,200-per-minute per-user limit remains.
Affected users
Who needs to care
Forge app developers and operators whose user-led invocation traffic is bursty or was constrained by the former installation or environment limits.
Required response
What to do
Recalculate throttling and load-test assumptions against both installation windows, preserve the unchanged per-user guard, and stop relying on the removed environment-wide limit.
Evidence boundary
What the source does not prove
Atlassian proves the stated user-led invocation limits and removal of the environment cap. It does not change other Forge rate limits, guarantee throughput below the caps, or waive product-specific and downstream service limits.
Lifecycle history
Dated event sequence
- User-led invocation limits rebalanced
Atlassian raised the installation minute allowance, added a 300-requests-per-second ceiling and removed the environment-wide limit while retaining the per-user limit.
Evidence ledger
First-party sources
- 01Atlassian Developer — Forge changelog — user-led invocation rate limits
Official Forge rate-limit and enforcement authority · 2026-09-01
Open official source ↗