cancel_retry_named
Call v151 → current #9Remove the retry configuration from a named scheduled task.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with cancel_retry_named, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch which emits events: RetryCancelled and modifies storage: Retries, 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
Ergonomic retry cancellation for named tasks using the task name.
Use Cases
- Disable retries for named tasks
- Clean up retry configurations
From Chain Metadata
Cancel the retry configuration of a named task.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | id | [u8; 32] [32] | id ([u8; 32]) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Named task exists in Lookup
- Task has retry configuration
Effects
Events Emitted
Postconditions
- RetryConfig removed
- Task will not retry on failure
Side Effects
- Emits RetryCancelled event
Code Examples
import { ApiPromise, WsProvider } from "@polkadot/api";
import { stringCamelCase } from "@polkadot/util";
const provider = new WsProvider("wss://entrypoint-finney.opentensor.ai:443");
const api = await ApiPromise.create({ provider });
// Build cancel_retry_named call
const id = 0;
const call = api.tx[stringCamelCase("Scheduler")][stringCamelCase("cancel_retry_named")](
id
);Runtime Info
- Pallet Index
- 15
- Call Index
- 9
- First Version
- v151
- Current Version
- v393