Skip to Content
Puppi

Read a run

Print an attempt's status, timings, and logs.

puppi logs prints one run: each attempt’s status, how long the steps took, the error, and the lines from ctx.log.

puppi status --env prod
puppi logs <run-id> --env prod
puppi logs <run-id> --env prod --json

Environment flags are in the CLI reference.

puppi status is the latest run. Pass --run <id> to select another. The engine keeps the newest 100 runs on the list route.

Attempt status

StatusMeaning
runningThe attempt has not settled.
successThe producer finished and the checks passed. latest moved.
failedThe producer failed. error_class is retryable or terminal.
failed_by_checkA blocking check failed after the write. latest stayed on the previous result.
skippedNothing new arrived, or the asset was already current.
blockedAn upstream in this run failed or was blocked, so this asset did not build.
cancelledThe attempt was cancelled.

A run’s status is queued, running, success, failed, or cancelled. queued means a run of the same plan is already in flight, and this one waits for it.

The error and the log

error_class is retryable or terminal. A retryable failure may already have been followed by a later attempt with a higher number. The message on the last one includes gave up after … when the budget is spent. See Rate limits and retries.

A check failure looks like this:

check failed: column email missing

ctx.log lines are on the attempt, with a level of debug, info, warn, or error. Secret values are scrubbed before the line is stored. --json prints the attempt objects from GET /api/v1/runs/<id>, including timings, logs, error_class, and error_message.

A worker in strict residency does not send the text of a log line, an error message, a custom check’s detail, or a string attribute on a user span. puppi logs prints that line as kept on the worker. The error class still arrives, so a retry is still decided from it. Counts, schema, and lineage still arrive.