shipper_resume_issue
shipper_resume_issue
Section titled “shipper_resume_issue”Clear a pending or durable operator pause without changing the current worker, workflow stage, or repository Auto-ship intent.
When to use
Section titled “When to use”Use to cancel a pending Pause request or clear a durable operator pause. Resume leaves workers, workflow state, and Auto-ship intent unchanged and is idempotent when no pause exists.
Behavior hints
Section titled “Behavior hints”- readOnlyHint: false — The tool may intentionally modify repository or workflow state.
- destructiveHint: false — The tool is not expected to remove or rewrite workflow artifacts.
- idempotentHint: true — Retrying the same call is expected to be safe once the target state is reached.
- openWorldHint: false — The tool does not reach GitHub or other external systems outside the MCP server.
Input schema
Section titled “Input schema”| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| issue | integer | string | yes | - | Shipper issue reference. S# |
Output schema
Section titled “Output schema”object
Example call
Section titled “Example call”{ "issue": "S#42"}Example result
Section titled “Example result”{ "status": "resumed", "issue": "S#42", "pause": { "state": "none" }, "changed": true, "cleared": "pending"}Error modes
Section titled “Error modes”- Local issue-state replica not initialized: Local issue-state replica is not initialized for owner/repo. Run
shipper issue reconcile --repairto import/reconcile it. - Local issue-state replica present but not fully reconciled: Local issue-state replica is present but not fully reconciled for owner/repo. Run
shipper issue reconcile --repairto import/reconcile it. - Local issue-state replica schema unsupported: Local issue-state replica has an unsupported schema for owner/repo. Locally reconstructable older replicas migrate automatically on first issue-state access. Run
shipper issue reconcile --repairfor supported local-ID V3 blocker imports requiring GitHub data or ordinary current-store repair. Numeric snapshots inissues/<GitHub-number>.jsonor_pending-blocker-imports/legacy/<GitHub-number>.jsonrefuse the entire store, listing all affected records and leaving existing local issue state unchanged. This Shipper version no longer migrates GitHub-number issue snapshots. Use a Shipper release from before this change to migrate the store before retrying this version. Fresh or recreated stores retain initial blocked-state imports and interrupted-import retries after metadata becomes reconciled; local-ID V3 stored blocker lists can complete locally in store-only mode. - Local issue-state replica malformed: Local issue-state replica is malformed for owner/repo. Run
shipper issue reconcile --repairto import/reconcile it. - Running issue-state reader stale: The running Shipper issue-state reader is stale for owner/repo: observed store schema v10 is newer than supported schema v9. Restart or reconnect the MCP client and server. If a freshly launched server remains incompatible, update the installed Shipper release or rebuild the source checkout before reconnecting. Preserve the issue-state store unchanged.
- Invalid or unready repository target: Repository identity could not be established for
. The repository has no commits. Create an initial commit. Correct this condition and retry the repository read with repository_path.