cancel_named
Call v133 → current #3Cancel a scheduled task by its unique name identifier.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with cancel_named, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch which emits events: Canceled and modifies storage: Agenda, Lookup, and finally post-dispatch where ExtrinsicSuccess is emitted and fees are settled.
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Click items to navigate. Pan and zoom to explore.
Used by: developersanalytics
The Big Picture
Named cancellation is the ergonomic way to cancel tasks by name rather than block/index.
Use Cases
- Cancel governance proposals by ID
- Abort named operations cleanly
From Chain Metadata
Cancel a named scheduled task.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | id | [u8; 32] [32] TaskName | id ([u8; 32]) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Named task exists in Lookup storage
- Caller has permission
Effects
Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Build cancel_named call (typed, named args)
const id = "0x0000000000000000000000000000000000000000000000000000000000000000";
const tx = api.tx.Scheduler.cancel_named({
id,
});Runtime Info
- Pallet Index
- 15
- Call Index
- 3
- First Version
- v133
- Current Version
- v411