Limits
Oktul Code Studio's limits on run time, requests, memory, events and storage, each with the Forge limit or the decision behind it.
Most of Oktul Code Studio’s limits are Atlassian Forge’s own; the rest are decisions, each with its reason. The one a script meets most often is the request budget for other systems.
| Limit | Value | Why |
|---|---|---|
| Longest run | 900 seconds per invocation, then at most three automatic continuations: about an hour | Forge’s invocation limit; three continuations by decision, so a loop does not run for ever |
| Stopping a run | Within 7 seconds of a stop, a tight loop with no await included |
The run reads its stop every 5 seconds; a script that does not stop in the next 2 is ended |
| Requests to this site | 5,000 a run | Code Studio’s own cap |
| Requests elsewhere | 1,500 a run, 100 per runtime minute | Forge’s egress budget. Requests to this site’s own gateway are routed through Forge and do not count |
| Script memory | 256 MB, with a 256 KB stack. A run whose function passes 900 MB ends with a memory error | Code Studio’s sandbox, inside the run function’s 1,024 MB. The run ends before Forge would end the function |
| Nesting | A value nested more deeply than the engine can follow ends the run with that error | QuickJS’s own stack |
| A WebAssembly call | 30 seconds, and the module’s memory at most 128 MB | Checked when the module is saved |
| Event delivery | Up to 3 minutes after the change; an event over 200 KB is not delivered | Atlassian’s product events |
| Listener chains | The eleventh run in a chain of runs triggering each other is stopped | As ScriptRunner stops its eleventh self-triggered run |
| Event types with listeners | 100 per site | Forge’s dynamic modules. Work item events do not count against it |
| Automation and API trigger wait | 45 seconds, then the run carries on and is read later | Forge’s 55-second limit for those modules |
| Run retention | 1 to 90 days, 10 by default | Site settings |
| Revisions | The 20 newest and none past a year, never the draft or a revision ever published | Storage |
| Repository pull | 80 files a pull | The egress budget of one invocation |
| Configuration import | 4 million characters; a zip at most 10,000 files and 64 MB unpacked | One resolver call |
| Storage throughput | 4,000 reads and 4,000 writes a minute per site | Forge’s key-value store; the ceiling a busy site meets first |
Common questions
- How long can a Code Studio script run?
- 900 seconds per invocation, then up to three automatic continuations: about an hour in all.
- How many requests can a script send?
- 5,000 to this site and 1,500 to other systems in one run, at most 100 a minute to other systems.
- How long are runs kept?
- 10 days by default, set between 1 and 90 days in the site settings.
Related
A problem or a question? Write to support@oktul.com or open a request in the Help Center (opens in a new tab).