Automation Limits
Understand execution budgets, feature restrictions and errors in Lua automations.
Each run uses an isolated Lua sandbox with bounded execution. Limits cover instructions, elapsed time, memory, output, reads, object creation and mutations. Individual operations can have additional limits. A script also needs the feature permissions and editor context required by each method.
Read the run error
Inspect Output, results and Automation History when a run stops. A syntax error, unavailable feature, unsupported object and exhausted budget require different corrections; repeatedly running the same source does not remove a limit.
Reduce work
Narrow queries and selections before looping. Reuse read results instead of repeating the same query for each object. Split a large design change into smaller intentional runs and inspect each result.
Use supported access
Use documented app API methods. The sandbox removes unsafe system and file-loading facilities and does not provide unrestricted browser, file-system or network access. It cannot bypass account permissions or edit unavailable contexts.
Check the current reference
Use Help and its API/runtime documentation for current method and budget details. Host-specific limits can differ; avoid designing a script around an assumed fixed maximum. Stop a run when needed and inspect the canvas and reported result before continuing.