- Revisions tab: click Deploy new revision after changing the image or settings, and click Roll back to this to go back to an earlier version.
- Variables tab: see the environment variables and secrets (up to 100). This tab is read-only; to change them, click Edit by deploying a revision, which creates a new revision.
- Overview page: the Instance row shows the container’s status and latest error.
- Logs tab: the latest output your app wrote to stdout and stderr. Filter the text, show only stderr, or turn on auto-refresh. About the last 16 MB is kept, and a new deploy starts a fresh log.
If an Invoker token is required, callers must send the token in the Authorization or X-Serverless-Authorization header. The token is shown only once for copying.
If something goes wrong
The app shows 502 “No response”
This is usually a port mismatch. Your app must listen on 0.0.0.0 on the port you set (read it from $PORT), not on localhost.
It shows 503 “Temporarily unavailable”
The app stopped while starting, or failed the health check. See the reason in the Instance row on the Overview page and in the Logs tab. Check the command and variables. The health check path must respond with a status below 500. If the page says “This service is stopped.”, the container has been stopped: start it. If it says “This service is suspended.”, the service is on hold, for example for unpaid usage (see Not enough money in your wallet).
It shows 504 “Took too long”
The request took longer than the timeout you set. Increase the timeout under Deploy new revision, in the Scaling step (up to 3600 seconds), or move long-running work to the background.
It shows 429 “Too many requests”
All instances are busy at the maximum number. Increase max instances or concurrency.
It shows 401 “This service requires a valid invoker token.”
This service requires a token. Send the token in the header, or change access to Public.
It shows 403 “This service only accepts traffic from inside its own project network.”
This service only accepts traffic from inside the VPC. Call it from a service in the same project, or change Ingress to all (Internet).