View logs

Repster captures full output from every run: locally in SQLite, and in the cloud via the control plane.

CLI

rp logs                          # logs from the most recent run
rp logs --run <run-id>           # logs for a specific run
rp logs --flow <flow-name>       # logs from the most recent run of a specific flow
rp logs --profile prod           # logs from a cloud profile

rp logs without arguments shows the most recent local run. Use --profile to target cloud runs.

Check run status first

rp status                        # last N runs (local + cloud combined)
rp status <flow-name>            # filter by flow name (positional)

The status command shows run ID, trigger (scheduled/manual), status (pending/running/succeeded/failed/cancelled), and start time.

Web UI

Runs, status, and searchable log output are also available under Runs, locally at localhost:8080 (rp dev), or in the Repster Cloud UI (repster.online) for cloud runs.

Understanding log output

Log output is the full stdout/stderr from the dlt pipeline run: progress and row counts, your own print()/logging output, and the complete traceback on failure, so you can debug without access to the worker environment.

Retrying a failed run

rp retry                         # retry the most recent failed run
rp retry --run <run-id>          # retry a specific run
rp retry --flow <flow-name>      # retry the most recent failed run of a flow

The retried run is linked to the original run in the run history.