opschain admin migrate-logs status
Included from Basic tier
Reports the backfill's durable state from any machine: both phase rows
(migrate and purge), each with its state (idle, running, paused or
completed), counters (owners verified, lines and bytes written, owners
failed, groups skipped, owners and lines purged), the responsible worker
replica, the last error when a phase paused itself, and the planner's
log_lines row estimate (pg_class.reltuples — an estimate, not a count,
there to gauge progress without scanning hundreds of millions of rows).
A running migrate phase advances one batch per tick on the cron leader; a
phase that hit an error sits paused with the error on its row — fix the
cause and resume. completed on the migrate phase means every discoverable
owner is verified in segments (migration-complete); completed on the purge
phase means every verified owner's source rows are gone (purge-complete).
Flags
| Flag | Meaning |
|---|---|
--server <url> | Server base URL (default: the active context / OPSCHAIN_SERVER). |
--auth-token <token> | Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login). |
Output is a human summary; -o json or -o yaml prints the full document.
Exit codes
| Code | Meaning |
|---|---|
| 0 | The status was reported. |
| 1 | Request failed, the token was rejected, or the store is not PostgreSQL. |
| 2 | Usage error — no server or no credential resolvable. |
Examples
opschain admin migrate-logs status
opschain admin migrate-logs status -o json
See also
opschain docs cli/admin-migrate-logs— the lane overview and space posture.