InvalidRoundNumber
Error v216 → current 26.4The pulse round number is invalid or out of expected sequence.
Encountered by: validatorsdevelopers
Why This Error Exists
Pulse rounds should generally progress sequentially. This error indicates the submitted round number doesn't fit expectations - perhaps it's a duplicate, too old, or out of order beyond tolerance.
Deep Dive
The chain may enforce round ordering or reject duplicates. If you submit round 100 but LastStoredRound is already 100, that's a duplicate. If LastStoredRound is 50 but you submit round 30, that might be too old.
Debugging Example
You submit pulse for round 12345678. Error: InvalidRoundNumber. Query LastStoredRound() returns 12345678 - it's already stored! Fetch a newer round from Drand.
Prevention Tips
- Always check LastStoredRound before submitting
- Fetch the latest round from Drand, not cached values
- Handle race conditions where another worker submitted first
From Chain Metadata
the round number did not increment
What This Means
The pulse round number is invalid or out of expected sequence.
Common Causes
- Submitting an old round that's already been recorded
- Round number is before OldestStoredRound
- Round number jumps unexpectedly (missing intermediate rounds)
How to Fix
- Query LastStoredRound to see what's already submitted
- Check OldestStoredRound for the valid range floor
- Ensure offchain worker fetches the latest, not cached, rounds
Storage to Check
Thrown By
Runtime Info
- Pallet Index
- 26
- Error Index
- 4
- Error Code
- 26.4
- Runtime Version
- v393