TargetBlockNumberInPast
Error v133 → current 15.2You're trying to schedule a call for a block that has already passed.
Encountered by: developers
Why This Error Exists
Scheduled tasks must target future blocks. For immediate execution, submit the call directly.
From Chain Metadata
Given target block number is in the past.
What This Means
You're trying to schedule a call for a block that has already passed.
Common Causes
- Target block number is less than or equal to current block
- Delay calculation error
- Stale transaction submitted after target passed
How to Fix
- Use a future block number
- Use schedule_after with a positive delay
- Recalculate target based on current block
Storage to Check
System.Number (removed)
Runtime Info
- Pallet Index
- 15
- Error Index
- 2
- Error Code
- 15.2
- Runtime Version
- v393