Runtime changelog, 27 October 2026

What shipped in Runtime Cloud on 27 October 2026: CI/CD reports a job lost with its machines as "Could not run"; sandboxes reach each other by name on every server; and every API response includes a Server-Timing header.

CI/CD reports a job lost with its machines as "Could not run"

When a job's task is lost on three machines without reporting a result, the job now ends as Could not run with the reason (for example, "Lost 3 times, never reported; the last on : no answer for 265 s"). Previously it was reported as "Failed in 0.0 s: exit code 1" and annotated on a file it never tested. A test failure in the same job still fails it. Lost runs are no longer recorded as test failures in flaky-test history.

Sandboxes reach each other by name on every server

A sandbox can now connect to another sandbox in its organization at <name>.sandbox.internal whichever server runs either one; before, only sandboxes on one server could. Private networks (WireGuard) are reachable from sandboxes on every server too. Connections by name have a daily allowance of 100 GiB for each target sandbox, separate from the private network's 50 GiB. When the private network is briefly unavailable from a server, connections to it return 503 with private-network-unavailable and are never sent anywhere else; retry after a minute.

Every API response includes a Server-Timing header

The header, Server-Timing: app;dur=12.3, gives the time in milliseconds from when the API received the request until its response headers were ready. Subtract it from the time your client measured to get the network's share of each call (the API).