schedule_after

Call v133 → current #4

Anonymously schedule a 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

Convenience for relative timing - specify delay rather than absolute block number.

Use Cases

  • Schedule operations with relative timing
  • Implement delays without calculating blocks

From Chain Metadata

Anonymously schedule a task after a delay.

Input Parameters

#NameTypeDescription
0
after
u32 after (u32)
1
maybe_periodic
Option maybe_periodic (Option)
2
priority
u8 priority (u8)
3
call
RuntimeCall call (RuntimeCall)

Permissions

Origin
Unknown
Required Role

Permission data inferred from metadata. May be incomplete.

Requirements

  • Caller has permission
  • Delay is at least 1 block

Effects

Events Emitted

Storage Modified

Postconditions

  • Call scheduled for current_block + after
  • Task added to Agenda

Side Effects

  • Equivalent to schedule(when=current_block+after)
  • Deposit may be reserved

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_after call
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_after")](
  after,
  maybe_periodic,
  priority,
  call
);

Runtime Info

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