We will change the current invocation rate limit from a per-minute fixed window to a per-second sliding window very soon. In line with this, we'll also scale the limit accordingly.
For more information, refer to our changelog.
Limits how many times your app’s functions can be invoked and the maximum duration each invocation can run.
An app can be invoked by users, webtriggers, or scheduled triggers. The following limits apply to all three:
| Resource | Limit | Description |
|---|---|---|
| Invocation rate limit | 1,200 | Maximum number of invocations per one minute sliding window. That is, an app reaches this limit when it is invoked 1,200 times within the last 60 seconds. |
| Runtime seconds (also includes UI modules invoked by Forge Remote) | 25 | Maximum runtime permitted before the app is stopped. |
| Runtime seconds (events invoked by Forge Remote) | 5 | Maximum runtime permitted before the app is stopped. This applies to remote back ends receiving events from the Atlassian platform. |
| Runtime seconds (async events and scheduled trigger module) | 900 | This applies to function modules that are only referenced by consumer or scheduled trigger modules. Default timeout is 55 seconds. Use timeoutSeconds to extend it. |
| Runtime seconds (web-triggers) | 55 | Maximum runtime permitted before the app is stopped. |
| Single outbound request timeout (async events) | 180 | Maximum time a single outbound request can take before being terminated. Outbound requests refer to fetch requests, including both Atlassian app REST API and external API requests. This limit can only be reached using long-running functions. |
| Log lines per invocation | 100 per runtime minute (rounded up) |
Maximum number of log entries for an invocation.
The limit is calculated based on the function timeout, specified by timeoutSeconds, rounded up per minute.
|
| Log size per invocation | 200 KB | Maximum size of all log line data generated per invocation. |
| Log file size per download | 100 MB | Maximum file size of filtered logs per download. |
| Log lines per download | 96,000 | Maximum number of log entries per download. |
| Egress requests | 100 per runtime minute (rounded up) |
Number of network requests per invocation, excluding those made using requestJira or requestConfluence.
The limit is calculated based on the function timeout, specified by timeoutSeconds, rounded up per minute.
|
| Egress requests | 50,000 requests per minute, per app for egress calls | The maximum number of requests per minute that an app can make for egress calls, excluding those made using requestJira or requestConfluence. |
| Network requests | 3,000,000 requests per minute, per app and 100,000 requests per minute, per app, per tenant | The maximum number of requests per minute that an app can make for network calls, including those made using requestJira or requestConfluence. |
| Memory | 1,024MB | Available memory per invocation. |
| Front-end invocation request payload size | 500KB | The maximum request payload size for a front-end invocation (for example, invoke and invokeRemote via @forge/bridge). |
| Front-end invocation response payload size | 5MB | The maximum response payload size from a front-end invocation (for example, invoke and invokeRemote via @forge/bridge). |
If your app is still running on the previous runtime version, it only has 128MB of available memory per invocation.
We strongly recommend all Forge developers to use the current runtime. For details about the previous runtime (including instructions for migration), see Upgrading from legacy runtime.
Rate this page: