Agenda
Storage Map v133 → currentItems to be executed, indexed by the block number for execution.
Explore chainQueried by: developersanalytics
The Big Picture
The core scheduling data structure. Each block number maps to a bounded vec of tasks to execute.
Use Cases
- See what's scheduled for a block
- Monitor scheduled operations
- Build scheduling dashboards
From Chain Metadata
Items to be executed, indexed by the block number that they should be executed on.
Purpose & Usage
Purpose
Main storage of scheduled tasks - queried to see what will execute at each block.
Common Query Patterns
- Query by block number to see scheduled tasks
- Iterate to list all scheduled tasks
Query Keys
| # | Name | Type | Description |
|---|---|---|---|
| 1 | key1 | u32 | key1 (u32) |
Stored Value
value (BoundedVec)
Relationships
Related Events
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 });
// Query Agenda storage
const key1 = 0;
const result = await api.query
[stringCamelCase("Scheduler")]
[stringCamelCase("Agenda")](
key1
);
console.log("Agenda:", result.toHuman());Runtime Info
- Pallet
- Scheduler
- Storage Kind
- Map
- First Version
- v133
- Current Version
- v393