opschain admin migrate-logs resume
Included from Basic tier
Resumes the paused phase — the purge when one is paused, otherwise the migration — from its durable cursor, and refuses when nothing is paused. The cursor and all counters live in the database, so a resume works from any machine, after a server restart, and after an HA failover: the new cron leader picks the sweep up where the old one stopped, and already-verified owners are skipped from the evidence table.
A phase that paused itself on an error resumes the same way once the cause is fixed; the error is cleared from the state row.
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). |
Prints the status document after the flip (-o json / -o yaml).
Exit codes
| Code | Meaning |
|---|---|
| 0 | The phase was resumed. |
| 1 | Refused (nothing is paused), request failed, or the token was rejected. |
| 2 | Usage error — no server or no credential resolvable. |
Examples
opschain admin migrate-logs resume
See also
opschain docs cli/admin-migrate-logs-pause— the other half of off-peak windowing.