---
title: "Revisions and traffic"
description: "Every deploy makes an immutable revision; traffic is split between revisions by percent."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.ezghcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Revisions and traffic

## Revisions

A revision is a service's settings at one deploy. Changing any of these makes a new revision:

| Field | Values | Default |
| --- | --- | --- |
| `image` | A tag or digest in the project's [Container Registry](/registry) | Required |
| `port` | 1 to 65535 | 8080 |
| `vcpus` | 1, 2, 4, 8 | 1 |
| `memoryMiB` | 512, 1024, 2048, 4096, 8192, 16384 | 512 |
| `diskGiB` | 1 to 50 | 5 |
| `env` | Up to 64 variables, 32 KiB in all; not `PORT` or names starting with `EZGH_` | None |
| `bot` | A [bot](/iam/bots) whose short-lived keys code in the instance gets | None |
| `egress` | `internet`, `vpc` or `none`: see [Outbound network](/run/egress) | `internet` |
| `maxConcurrency` | 1 to 1000 | 80 |
| `minInstances`, `maxInstances` | 0 to 100, and 1 to 100 | 0, 10 |
| `requestTimeoutSeconds`, `startupTimeoutSeconds` | 1 to 3600 | 300, 240 |

- A deploy's tag is resolved to a digest then: deploying the same tag again picks up what was
  pushed to it. The image must be in the service's own project.
- `env` values are never shown again: revisions list only the variables' names. A change sets the
  whole environment; leave `env` out to keep the latest revision's.
- A change (`PATCH`) takes the latest revision's settings and changes what it names.

## Statuses

| Status | Means |
| --- | --- |
| `deploying` | No instance of it is ready yet |
| `ready` | An instance started and was ready. It can take traffic |
| `failed` | It couldn't start: the reason is in its `scalingError`. It takes no traffic, and the previous revision keeps serving |
| `retired` | It's ready but has no share of the traffic. It has no instances |

A service keeps its last 100 revisions; older retired and failed ones are deleted. You can delete
a retired revision, or a failed one that isn't the latest, yourself.

## Traffic

A service's traffic is a list of shares that add up to 100:

```json
[{ "revision": "latest", "percent": 90 }, { "revision": "rrv_k3f9a0x2m7qp", "percent": 10 }]
```

- `latest` is the service's latest ready revision: a share on it moves to each new revision once
  that revision is ready. The default is 100% to `latest`.
- A revision's ID pins a share to that revision. Naming a retired revision again brings it back: a
  rollback.
- Changing traffic or access makes no revision and takes effect at once.

```sh
ezgh run traffic web latest=90 rrv_k3f9a0x2m7qp=10
```

In the console, a service's **Actions** › **Edit traffic** saves once the shares add up to 100.

Source: https://docs.ezghcloud.com/run/revisions-and-traffic/index.mdx
