retry

manifold ops retry --op-id <op_id> [flags]

Dry-run by default. With --apply, POSTs /v1/ops/:opId/retry and returns the op to the pending queue.

Flags

--op-id <op_id>

Required identifier of the op to reset. Copy it from ops pending or the admin panel.

Example:

manifold ops retry --op-id op_123

--apply

POST the retry request and return the op to the pending queue. Without this flag, the command only shows which op would be retried.

• Default: false

Example:

manifold ops retry --op-id op_123 --apply

--api-token <token>

Personal API token used to retry the op. Falls back to MANIFOLD_TOKEN.

Example:

manifold ops retry --op-id op_123 --api-token "$MANIFOLD_TOKEN"

--api-origin <url>

Personal API origin to call.

• Default: https://manifold.jfa.dev/api (or MANIFOLD_API_ORIGIN)

Example:

manifold ops retry --op-id op_123 --api-origin https://manifold.example/api

Usage

manifold ops pending
manifold ops retry --op-id <op_id>
bun run manifold ops retry --op-id <op_id> --apply

Blocked ops (usually after ~5 failed attempts) are the usual candidates. After retry, mangadex:* ops drain on the Worker; anilist:* ops still need a device drain.