Named
Error v133 → current 15.4You used a non-named function on a named task, or vice versa.
Encountered by: developers
Why This Error Exists
Named and anonymous tasks have separate APIs. Named tasks are identified by a 32-byte ID stored in Lookup.
From Chain Metadata
Attempt to use a non-named function on a named task.
What This Means
You used a non-named function on a named task, or vice versa.
Common Causes
- Using cancel on a named task (should use cancel_named)
- Using cancel_named on an anonymous task
- Task was created with schedule_named but modified with schedule
How to Fix
- For named tasks: use cancel_named, set_retry_named, cancel_retry_named
- For anonymous tasks: use cancel, set_retry, cancel_retry with (block, index)
- Check Scheduler.Lookup to verify if task has a name
Storage to Check
Runtime Info
- Pallet Index
- 15
- Error Index
- 4
- Error Code
- 15.4
- Runtime Version
- v393