Skip to main content
Engineering

Not translated yet — showing English.

Functions

Functions is where you watch and operate your game's server-side code. It shows every function's health and replicas, its environment variables and secrets, runtime settings, deploy history and logs. Code gets here through the PlayServ CLI; the Backoffice runs, configures and observes what you deployed. The page is scoped to the environment selected in the top bar.

Pooled and self-hosted game servers aren't listed here

Functions lists cloud functions and game servers that PlayServ runs on Cloud Run. Game servers on a machine pool or on your own machines have nothing to deploy or scale here; they live in Servers.


Overview

One row of figures for the whole environment.

FigureWhat it shows
Functions liveFunctions currently serving traffic.
Replicas runningRunning instances, and across how many regions.
Invocations 24hCalls in the last 24 hours.
Error rate 24hShare of failed calls: within target up to 1%, elevated above 1%, above threshold above 5%.
P95 latency 24h95th-percentile response time: a warning from 200 ms, critical above 800 ms.

The functions list

Each row shows the function's language, name, status, replicas, 24-hour invocations and error rate, P95 latency, and when it was deployed with which revision. Search by name, handler or trigger, and filter by Status, Trigger and Runtime.

StatusMeaning
liveDeployed and serving traffic.
stagedDeclared, with no code deployed yet.
failingThe last build failed, or a secret the function declares has no value in this environment.
disabledStopped by an operator. It accepts no calls; its code and data stay.
deletedRemoved from the environment.

New functions are created by deploying them with the CLI, or by a push to a bound branch. New function in the Backoffice is coming soon. To connect a repository, use Project settings → Deployment: the Connect repo button on this page still shows coming soon.


A function

Click a function to open its panel. The header shows its name, trigger, when it was deployed and from which revision. The panel has four tabs, and its footer offers Disable (or Enable) and Delete.

Status

BlockWhat it shows
Status · Auth · Last invocationWhether it serves traffic and since when; whether callers need a signed-in player; whether it was called recently.
Replicas · 24h invocations · 24h error rateRunning replicas out of the maximum and the scaling policy; calls and failures in the last 24 hours.
VersionsThe latest deploy and any version tags serving next to it.
ReplicasEvery running replica with its region and resource use. Select one to see At a glance: status and uptime, region, memory against its limit, average CPU over 15 minutes, the deploy it runs, and its last error. Below it, a live tail of that replica's logs.

Scale opens the scaling dialog: a manual policy with a fixed number of replicas, or auto with a minimum and a maximum. Cloud Run replaces a function's instances itself, so individual replicas can't be restarted or stopped.

Scaling set here resets on the next deploy

The scaling spec in platform.json wins at deploy time. Change it there, too, if the new values should stay.

Bindings

Everything injected into the function at runtime.

ColumnEnvironment variables
NameThe variable, for example LOG_LEVEL.
Effective valueWhat the function actually receives.
Manifest defaultThe value from platform.json; read-only here.
Override (this env)A value for this environment only, edited inline.
ColumnSecrets
NameThe secret the function declares, for example STRIPE_API_KEY.
Statuslinked when it has a value in this environment, missing when it hasn't been set. A missing secret leaves the function failing.
RotatedWhen its value last changed.

Rotate replaces a secret's value: paste the new value, and functions that use it pick it up. Values are never shown. The project-wide Bindings tab at the top of Functions shows every function's variables in one table, and a Secrets card: Add secret there gives a missing secret its value, and a secret no function uses any more can be deleted.

Settings

SettingValuesDefault
Memory tierLight 128 MB · Standard 256 MB · Heavy 512 MB · XL 1 GB · 2XL 2 GB—
TimeoutUp to 3600 s per call60 s for a cloud function, 3600 s for a game server
Max concurrency1–1000 calls at once per replica80 for a cloud function, 1000 for a game server
Scalingmanual · N replicas or auto · min–max; changed with ScaleFrom platform.json
Auth requirementplayer: callers must be signed-in players. none: no player needed.From platform.json

Every call needs an API key either way; who may call a function at all is set by execute in its manifest. A denied caller gets 403 function_execute_forbidden, and a call without the required player session gets 401 player_auth_required. Settings are saved without a redeploy.

Deploys

Every build of this function, newest first, with when it was deployed, its revision, who deployed it and how the build went. The list is read-only: deploys come from the CLI.

StatusMeaning
queued · building · deployingIn progress.
liveServing traffic. Locked.
drainingThe previous version, finishing in-flight calls while traffic moves to the new one.
archivedA past version. You can roll back to it with playserv functions rollback.
failed · cancelledDidn't go live.

The delete action purges an archived, failed or cancelled deploy.


Version tags

A tag deploys a second, addressable version next to the latest. Normal traffic keeps going to the untagged latest; a caller reaches the tagged version by sending X-Playserv-Function-Version: <tag> on the call.

An unknown tag fails with 404 function_version_not_found instead of falling back to latest. Inside the function, the tag that served the call arrives in the same X-Playserv-Function-Version request header (req.ServingVersion in C#); it is absent when latest served it. Tags are deployed with --tag on the CLI, see Deploying with the CLI.

A deploy can also be promoted to prod through the PlayServ API or MCP. A tagged deploy keeps its tag in the target environment, and an untagged one becomes its new latest.


Automatic deploys by branch

A push to a bound Git branch can deploy your functions to that branch's environment. Bind branches in Project settings → Deployment and add PlayServ's GitHub Action to the repository; every push to a bound branch then runs playserv publish for that environment.

The setup and the workflow are in Deployment → Branch deploys. Deploys made this way appear in History like any other.


Logs

A log stream for the whole environment. Pick one or more functions on the left; each line shows its time to the millisecond, level, function and message, and lines from the same call share a trace id.

ControlOptions
Time rangeLast 5 or 15 minutes, last hour, 4 or 24 hours, 7 days, today, yesterday, all time, or a custom range.
Levelinfo · warn · error · debug
SearchFull text across messages.
LiveStreams new lines as they arrive.

History

Every deploy that touched any function in the project, newest first: the revision, which function, who deployed it, when, and how long the build took. Filter with Time range. For now, History shows deploys in dev only.


Next steps

Last updated on 14 Oct 2026