Skip to main content
These are the hard limits that bound a single play run. They protect the platform (and your run) from runaway resource use, so a misbehaving play fails fast with a clear error instead of hanging or starving other work.
These values are generated directly from the runtime source, so this page is always current. Need a higher limit for a specific workload? Get in touch — most are raised per workspace.

Submit & input

Bundle & compile

Revision storage

Run duration

Inline composition & budgets

Concurrency

A play run has two independent concurrency layers: map rows (how many rows of a ctx.dataset().map(...) resolve at once) and external calls (provider tools and ctx.fetch; extra calls wait rather than fail). Map rows use a library default of 20 and accept a run-wide default/ceiling from 1 through 1000. External calls default to 64 and accept 1 through 256. Authored map concurrency, byte admission, provider pacing, and sandbox memory can tighten the effective values. Inline ctx.runPlay(...) shares both run limits.

Output & logs

Runtime sheet