AllNetworksInImmunity
Error Re-added v133 → v141, v142 → v145, v146 → v148, v149 → v150, v151 → v212, v216 → v216, v217 → v219, v233 → v315, v320 → v326, v334 → current 7.43All subnets are in their immunity period , so none can be pruned.
Why This Error Exists
New subnets get an immunity period during which they cannot be pruned, giving them time to bootstrap and prove value. When the network is at capacity and needs to prune a low-performing subnet to make room for a new one, this fails if ALL subnets are still in their immunity window. You must wait for some to become pruneable.
Deep Dive
NetworkImmunityPeriod is measured in blocks (often ~7 days worth). NetworkRegisteredAt(netuid) stores when each subnet was created. A subnet is immune if current_block - registered_at < immunity_period. When all subnets satisfy this condition, the network cannot make room for new ones through pruning.
Debugging Example
You call register_network(...) while SubnetLimit is reached. Error: AllNetworksInImmunity. Query each NetworkRegisteredAt(netuid) and compare to current_block - NetworkImmunityPeriod. All are within immunity. Find the subnet closest to losing immunity and wait for it to expire.
Prevention Tips
- Check subnet ages before planning subnet creation during high-demand periods
- Monitor AllNetworksInImmunity or compute it yourself from NetworkRegisteredAt data
- Consider acquiring an existing subnet instead of creating new when network is congested
From Chain Metadata
All subnets are in the immunity period.
What This Means
All subnets are in their immunity period, so none can be pruned.
Common Causes
- Many new subnets created recently
- Need to wait for immunity periods to expire
How to Fix
- Wait for subnet immunity periods to expire
- Check SubtensorModule.NetworkImmunityPeriod for duration
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 43
- Error Code
- 7.43
- Runtime Version
- v393