Skip to main content

​
Prerequisites

Run locally after authenticating. Find your application first:

​
Read and follow logs

Use Ctrl+C to stop following; this does not stop the app. The same commands work inside the workspace, where --follow polls every few seconds if the log stream isn’t available there. Check for exceptions, missing configuration, and whether the process binds the configured port. Runtime output can include application secrets, so review it before sharing.

​
Distinguish the failing stage

If the executable never started, read install/build/release logs. If the process runs but deployment fails readiness, compare the manifest with health requirements. If health succeeds but a browser cannot open the URL, check visibility and routing. For custom log sources and API streaming, follow the App Logs API.