Pause, resume or cancel a CPU job
Control one owned CPU validation job at its exact reviewed revision after approval, preserving request identity.
What you get
A revision-bound CPU control result with remaining work and any uncertainty.
Bounded CPU pilot control only; exact-action approval, current revision and account authority are required.
| Support | Requirement |
|---|---|
| Interfaces | MCP, HTTP |
| Access | approval required |
| Workflow state | qualified pilot |
| Credential corridors (see workflow) | resources |
Ask your assistant
Example task
Pause or cancel this CPU validation job after reviewing its current revision.Install this skill
Use an existing compatible MCP connection or the customer CLI. Skills provide instructions; installing them does not configure credentials, grant permissions or enable execution.
Install reliquary-cpu-control
reliqua skills install --skill reliquary-cpu-control --directory "$HOME/.agents/skills"Download SKILL.md — Official task instructions, version 0.5.0.
Install the customer CLI — Verified release downloads, commands and troubleshooting.
Connect MCP — Keep writes disabled for discovery and planning.
Authentication and exact scopes — Corridor names identify key configuration; the API checks its actual read and write scopes.
Follow the workflow
- Read the exact owned job for its current decimal revision and state. For resume also check current capabilities, submission grant and fresh worker availability.
- Present the chosen pause, resume or cancel action, exact revision and a concrete reason. Obtain explicit approval before job_control with approveExecution:true and a stable caller-supplied UUIDv4 idempotencyKey.
- HTTP uses POST /api/v1/jobs/{id}/pause, /resume or /cancel with schema_version:1, revision and reason, plus Idempotency-Key and X-Resource-Revision headers. Cancellation and pause drain or revoke in-flight authority; inspect the returned state.
- On conflict reload and review; on an unknown result preserve the original key and reviewed revision. Do not silently retry, substitute native administrator controls or change unrelated worker/miner operations.
Tools and API routes
Call reliquary_connection first and use only tools registered in that connection. Route templates need the owned resource identifiers described by the existing API reference.
| Interface | Operation |
|---|---|
| MCP | reliquary_connection |
| MCP | reliquary_jobs_capabilities |
| MCP | reliquary_job_get |
| MCP | reliquary_job_control |
| HTTP | GET /api/v1/jobs/capabilities |
| HTTP | GET /api/v1/jobs/{id} |
| HTTP | POST /api/v1/jobs/{id}/{action} |
Availability and authorization
This workflow can prepare an action using existing contracts. Execution requires current server capabilities, qualified capacity, appropriate account scope, a fresh quote when applicable, and explicit approval of the concrete action. The customer preview CLI has no execution commands; MCP writes stay disabled by default.
Back to the skills catalog — Find another workflow or connect an interface.