infoannouncementAtlassian calls it: Announcement
Updated invocation limits
- Announced
- APIs
- forge-core-platform
- Severity
- info, set by
reef/atlassian-rule-v1 - Source
- https://developer.atlassian.com/changelog/#CHANGE-3420
We’re updating the invocation rate limits for Forge apps to support larger-scale apps and platform stability.
What’s changing
The invocation rate limits for user-led invocations (UI and web triggers) are being updated to the following values:
- Per app installation: The limit is changing from 5,000 requests per minute (RPM) to 300 requests per second (RPS) or 7,000 RPM (whichever is hit first).
- Per environment: The previous global limit of 30,000 RPM is being removed to provide more flexibility for apps with large numbers of installations.
- Per user: The limit remains unchanged at 1,200 RPM.
What you need to do
If your app frequently performs high-burst activities, you may need to implement retry logic or optimize your function calls to stay within the 300 RPS threshold.
Retry logic can be implemented using:
- The
rateLimitPropertiesfield returned from Forge bridge invoke - Web trigger rate limiting response headers
For implementation examples and more details, see the Forge invocation limits documentation.
The text above is Atlassian's. reef added the severity, the dates it could read from the text, and the endpoints and scopes named in code.