Runtime changelog, 5 November 2026

What shipped in Runtime Cloud on 5 November 2026: a build whose identical image is larger than its maxImageMiB fails with the size to set; paused sandboxes started from a custom image survive the loss of their host; and a wake whose host does not answer fails within about a minute.

A build whose identical image is larger than its maxImageMiB fails with the size to set

When your account already had an identical image larger than a new build's build.maxImageMiB (8192 by default), the build failed with "The image could not be saved because of a fault on our side". It now fails immediately with An identical image of this organization is N MiB, larger than this build's build.maxImageMiB of M. Set build.maxImageMiB to at least N. Set build.maxImageMiB to at least that size and the build copies the identical image immediately.

Paused sandboxes started from a custom image survive the loss of their host

A paused sandbox started from your own image is no longer stopped when its host is lost, as long as its saved copy is complete and another host holds the image. Its next wake restores it from that copy on a host that holds the image. While no such host can take it, a wake returns 503 no_capacity with the detail that it starts from its saved copy as soon as one has room. If the image is deleted or rebuilt, or no other host holds it, the sandbox is stopped as before, and its parked charge ends when its host was lost.

A wake whose host does not answer fails within about a minute

A paused sandbox whose host did not answer its wake used to stay in resuming for as long as the host stayed silent, and every request on it waited. The wake now gives up after two unanswered attempts (about a minute): requests on the sandbox return 500 operation_failed immediately, its memory and files are kept, and nothing is charged. A minute later the host is asked again; once it answers, the sandbox is paused and the next request wakes it.