Fork sandbox
Fork the sandbox: checkpoint the running sandbox in place (it is briefly paused, snapshotted with its full memory state, and resumed on its node, keeping its ID and expiration untouched) and create count new sandboxes from that snapshot. Returns one result per requested fork, each carrying either the created sandbox or the error that prevented it from starting. A non-201 status means the request failed before any fork was attempted.
Anona: the sandbox is frozen only while its memory delta is written (about 0.1 s, longer right after it has touched a lot of memory) and then keeps running with its own ID and expiration. Each fork is a new sandbox: it takes a slot of your concurrent-sandbox limit and is billed like any other sandbox, and the forks inherit the source sandbox’s template, metadata, timeout policy and network policy, with the timeout of this request. count above the room left in your plan is not an error for the whole request: the forks that fit are created and each of the others carries 429 plan_limit_exceeded (with limit_name, limit, current and plan) in its own result entry, while a platform at capacity reports 503 per fork. A source sandbox that is not running is 409, and nothing is forked.