Runtime logs for failed deployments

Deployment detail now shows both build and runtime logs, so a deployment that builds successfully but then fails to start — a failed health check, a bad runtime config — gives you actionable output to debug.

Switch between build and run logs

A source select in the log header lets you switch between the Build and Runtime logs. Velumi picks the most useful one for you by default: the runtime log when the build produced an image, the build log otherwise.

Failed deployments now return their runtime logs instead of an access error, so a build-succeeds-then-fails deployment surfaces the output that explains what went wrong.

What went wrong

For failed deployments, the raw error and the AI failure analysis are now grouped into a single What went wrong card above the log, so the likely cause is the first thing you see. A Log complete indicator shows when a finished log has fully loaded.

Runtime logs are available for deployments that fail from this release onward.