# v2026.10.54

A busy server says so

When a server holds as much request data as it can, a call now waits up to 2 seconds and then answers `503 BUSY` with `Retry-After`, before anything is done. A run waits for room in the Code sandbox before it starts.

## What changed

- A new answer, `503 BUSY`, for a body that doesn’t fit in the server’s in-flight budget, and for a read of a run’s large data. See [`BUSY`](https://docs.gorunner.io/errors#BUSY).

## When you update

GoRunner’s image is private for now. With Docker, [sign in to the registry](https://docs.gorunner.io/self-host/install-docker#sign-in-to-the-registry) first. On Kubernetes, [sign Helm in and give the cluster its pull Secret](https://docs.gorunner.io/self-host/install-kubernetes#make-a-namespace). See [Update](https://docs.gorunner.io/self-host/update) for the whole procedure, or [Install with Docker](https://docs.gorunner.io/self-host/install-docker) and [Install on Kubernetes](https://docs.gorunner.io/self-host/install-kubernetes) to install this version anew.

**Docker**

```bash
# Check the image first: its Digest must be sha256:58cb2512820dce5ebee17db799d8ac2649741d07670e6df189e7bfec03992f91
docker buildx imagetools inspect ghcr.io/ralve-org/gorunner-selfhost:v2026.10.54

# Update
./deploy.sh v2026.10.54
```

**Kubernetes**

```bash
helm upgrade gorunner oci://ghcr.io/ralve-org/charts/gorunner --version 2026.10.54 -f values.yaml
```

## Going back

To go back, run `./deploy.sh v2026.10.53`. There is no migration, so no flag is needed.

Source: https://docs.gorunner.io/changelog/v2026.10.54