Limits
Limits that stop a run
Section titled “Limits that stop a run”A run that crosses one of these is stopped and recorded as failed.
| Limit | Value | Meaning |
|---|---|---|
banBucket |
60 s per server | Run time the organization earns per server, in seconds. Runs spend it; an empty bucket stops them. |
ctxCalls |
50 | Calls to ctx functions in one run. |
fuel |
50 ms | CPU time budget of one run. |
memory |
32 MB | Memory available to one run. |
stack |
262144 bytes | Stack size of one run. |
wallGuard |
60 s | Wall-clock limit of one run. |
Limits that refuse a call
Section titled “Limits that refuse a call”A call over one of these returns { ok: false, error } to the module, and the run goes on.
| Limit | Value | Meaning |
|---|---|---|
bansPerMinute |
10 | Bans all modules of one organization can issue per minute. |
fetchBody |
4 MB | Response body ctx.fetch reads; a larger answer is refused. |
fetchRedirects |
5 | Redirects ctx.fetch follows; each hop is checked again. |
fetchTimeout |
30 s | Time one ctx.fetch call may take, redirects included. |
kicksPerMinute |
20 | Kicks (AdminKick and AdminKickById sent through ctx.rcon) all modules of one organization can issue per minute. |