set_retry
Call v151 → current #6Configure retry behavior for a scheduled task if it fails.
View calls on chainCall Workflow
Click items to navigate. Pan and zoom to explore.
The Big Picture
Retry configuration lets failed tasks automatically reschedule rather than failing silently.
Use Cases
- Add resilience to scheduled operations
- Implement retry logic for transient failures
From Chain Metadata
Set a retry configuration for a task so that, in case its scheduled run fails, it will be retried after `period` blocks, for a total amount of `retries` retries or until it succeeds. Tasks which need to be scheduled for a retry are still subject to weight metering and agenda space, same as a regular task. If a periodic task fails, it will be scheduled normally while the task is retrying. Tasks scheduled as a result of a retry for a periodic task are unnamed, non-periodic clones of the original task. Their retry configuration will be derived from the original task's configuration, but will have a lower value for `remaining` than the original `total_retries`.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | task | (u32, u32) | task ((u32, u32)) |
| 1 | retries | u8 | retries (u8) |
| 2 | period | u32 | period (u32) |
Permissions
Permission data inferred from metadata. May be incomplete.
Requirements
- Task exists at (block, index)
- Period at least 1 block
Effects
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 set_retry call
const task = 0;
const retries = 0;
const period = 0;
const call = api.tx[stringCamelCase("Scheduler")][stringCamelCase("set_retry")](
task,
retries,
period
);Runtime Info
- Pallet Index
- 15
- Call Index
- 6
- First Version
- v151
- Current Version
- v393