On this page
Scripting
Limits
| Script | Time | Memory | Instructions | Modules |
|---|---|---|---|---|
| Playground and stored scripts | 5 s | 50 MB | 200 million | 16 |
| Workflow script nodes | 5 s | 50 MB | 200 million | 16 |
| Custom workflow actions | 5 s | 50 MB | 200 million | 16 |
| Incoming webhooks | the webhook's timeout, up to 30 s | 5 MB | 200 million | 16 |
| Custom app server functions | 5 s | 50 MB | 200 million | 16 |
| Workspace handlers | 5 s | 50 MB | 200 million | 16 |
| Portal handlers | 5 s | 16 MB | 500,000 | 64 |
| MCP tools | 5 s | 50 MB | 200 million | 16 |
| Archive jobs | 5 s | 50 MB | 200 million | 16 |
| Quote price tuning | 5 s | 50 MB | 200 million | 16 |
| Integration lifecycle hooks | the manifest's timeout_ms, up to 60 s |
50 MB | 200 million | 16 |
| Integration handler scripts | the manifest's timeout_ms, up to 60 s |
50 MB | 200 million | 16 |
| Integration server functions | the manifest's timeout_ms, up to 60 s |
50 MB | 200 million | 16 |
| Integration workflow actions | the manifest's timeout_ms, up to 60 s |
50 MB | 200 million | 16 |
| Integration API client setup | the manifest's timeout_ms, up to 60 s |
50 MB | 200 million | 16 |
| Integration upgrade scripts | the new manifest's timeout_ms, up to 60 s |
50 MB | 200 million | 16 |
| Integration extensions | the integration's timeout_ms, up to 60 s |
50 MB | 200 million | 16 |
| Data pipeline stages | 5 s | 50 MB | 200 million | none |
| Report preparation scripts | 5 s | 50 MB | 200 million | none |
| Portal component exports | 5 s | 16 MB | 500,000 | none |
| Scheduler penalty functions | 50 ms | 10 MB | 2 million | none |
| Product template resolvers | 5 s | 50 MB | 200 million | none |
| JDF and JMF templates | 5 s | 50 MB | 200 million | none |
Device HTTP responses
Device HTTP calls accept response bodies up to 1 MiB (1,048,576 UTF-8 bytes).
An oversized body or individual header returns ok = false with a size-limit
message before it enters Lua. The script can request a smaller page or handle
the failure; raising that returned message with error is catchable by pcall.
This does not make global execution-budget exhaustion recoverable.