schedule_named_after

Call v133 → current #5

Schedule a named task to execute after a delay from the current block .

View calls on chain

Click items to navigate. Pan and zoom to explore.

Used by: developersanalytics

The Big Picture

Combines named scheduling (easy cancellation) with relative timing (no block calculation).

Use Cases

  • Schedule named timeouts with relative delays
  • Create cancellable deferred operations

From Chain Metadata

Schedule a named task after a delay.

Input Parameters

#NameTypeDescription
0
id
[u8; 32] [32]id ([u8; 32])
1
after
u32 after (u32)
2
maybe_periodic
Option maybe_periodic (Option)
3
priority
u8 priority (u8)
4
call
RuntimeCall call (RuntimeCall)

Permissions

Origin
Unknown
Required Role

Permission data inferred from metadata. May be incomplete.

Requirements

  • Caller has permission
  • Name not in use
  • Delay at least 1 block

Effects

Events Emitted

Storage Modified

Postconditions

  • Call scheduled for current_block + after with name
  • Lookup entry created

Side Effects

  • Combines named scheduling with relative timing

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 schedule_named_after call
const id = 0;
const after = 0;
const maybe_periodic = 0 as any /* Option */;
const priority = 0;
const call = 0 as any /* RuntimeCall */;

const call = api.tx[stringCamelCase("Scheduler")][stringCamelCase("schedule_named_after")](
  id,
  after,
  maybe_periodic,
  priority,
  call
);

Runtime Info

Pallet Index
15
Call Index
5
First Version
v133
Current Version
v393