cancel_retry
Call v151 → current #8Remove the retry configuration from a scheduled task.
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with cancel_retry, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks, followed by dispatch which emits events: RetryCancelled and modifies storage: Retries, 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
Removes retry resilience from a task; failures will be abandoned without retry attempts.
Use Cases
- Disable retries when circumstances change
- Convert to fail-fast behavior
From Chain Metadata
Removes the retry configuration of a task.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | task | (u32, u32) | task ((u32, u32)) |
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Task exists at (block, index)
- Task has retry configuration
Effects
Events Emitted
Storage Modified
Postconditions
- RetryConfig removed from Retries storage
- 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 call
const task = 0;
const call = api.tx[stringCamelCase("Scheduler")][stringCamelCase("cancel_retry")](
task
);Runtime Info
- Pallet Index
- 15
- Call Index
- 8
- First Version
- v151
- Current Version
- v393