Services in the console

The Services section answers one specific question: how many processes exist in this project, what each one runs, and what condition they are in.

A project with a single service shows that service directly in the overview, without this layer — it exists for people who went looking for it. The four types and when to use each are in Services.

What the screen shows

The list separates what runs continuously from what runs at set times.

Information	What it means
Type	Web application, internal service, continuous process, or scheduled task
Replicas	How many instances are up, and how many were requested
Schedule	For scheduled tasks, in plain language: "every day at 03:00"
Command	The service's own command, when it has one
Address	For web applications, the address that answers

Internal values — the type's technical name, the schedule expression — live in each service's technical details panel, labeled as such.

The three absences

The screen uses three different texts on purpose, because they mean different things:

What you read	What it means
Not measured	The data has not arrived yet
No command of its own	Nobody defined one; the image's command applies
Receives no traffic	This service type does not have that capability

Collapsing the three into a grey dash would have you hunting for a button that does not exist — or waiting for a number that will never come.

Replicas

The instance count appears with three readings: how many were requested, how many are ready, and how many are up. They diverge during a deployment and converge when it finishes; persistent divergence means something is keeping the new instances from becoming ready — check the application logs.

Schedule

A scheduled task shows its time in plain language. When the expression cannot be translated with confidence, the screen says it could not describe it rather than guessing a time: a wrong time makes someone plan maintenance right on top of a run.

Next steps

• Services — the concept
• Resources and limits
• Observability