Reference
rebase run logs
Show run events, workflow step state, and captured stdout/stderr logs.
Synopsis
rebase run logs <run-id>
rebase run logs <run-id> --no-follow
rebase run logs <run-id> --jsonArguments
| Argument | Type | Description |
|---|---|---|
<run-id> | str | Run ID. |
Options
| Option | Type | Description |
|---|---|---|
--follow / --no-follow | bool | Follow until the run reaches a terminal state. Defaults to --follow. |
--poll-interval | float | Seconds between run status polls when following. Defaults to 1.0. |
--timeout | int | Maximum seconds to follow the run. Defaults to 600. |
--json | bool | Print raw event, step, and log JSON output. |
Output
Shows persisted run events, workflow step state (for workflow runs), and the run's stdout/stderr log lines. When following, new log lines stream in as they arrive; error-level lines are highlighted.
Log Availability by Run Type
| Target | Run type | Log source |
|---|---|---|
| Workflow | quick or long | Prefect's log API — includes print() output from workflow and step code. |
| Function or model | long | Cloud Run Jobs logs via Cloud Logging, correlated by job execution. |
| Function or model | quick | Cloud Run service logs via Cloud Logging, correlated by service revision and run markers. |
| Function or model | quick_shared | Not available yet — the command prints an explanatory message. |
Cloud Logging ingestion can lag by a few seconds, so lines may continue to appear briefly after the run finishes; the command performs a final fetch after the run reaches a terminal state.