tovuk check, tovuk deploy --dry-run, and deploy attempts.
Deploy diagnostics workflow
Check before creating a build
agent_instruction before creating another build.
Review dry-run warnings, enabled capabilities, meters, limits, and billing
estimates before deploy.Deploy and keep the returned ids
build_job.id, final_build.status, and deploy id from
the deploy output or deploy history. Keep those ids with the failing
command.Inspect build and runtime logs
Dashboard
The dashboard Activity view is available athttps://tovuk.com/account/activity
or https://tovuk.com/<handle>/activity. It shows recent deploys, recent
builds, runtime logs for a selected Service, next actions, and copyable agent
commands. Queued deploy rows can cancel queued build work and expose the same
tovuk deploy cancel <deploy_id> --json command. It uses the same activity,
deploy cancel, and log API routes, rate limits, and private account auth as the
CLI.
Agent commands
API
GET /v1/account/activityGET /v1/deploys/{deploy_id}POST /v1/deploys/{deploy_id}/cancelGET /v1/deploys/{deploy_id}/logsGET /v1/builds/{build_id}/logsGET /v1/services/{service_id}/logs
Meters and caps
Builds usebuild_minutes. Logs use log_events.
Rules
- Run
tovuk check --jsonbefore deploying. - Read the first actionable log error before making changes.
- Cancel superseded queued deploys.
- Include build id, deploy id, failing command, and first actionable log line in support tickets.