# disabled (/docs/errors/disabled) The call or feature is switched off: registration is closed on the subnet, commit-reveal (or the legacy direct path) is not enabled, transfers are disallowed by the subnet, the extrinsic is deprecated, or an admin has disabled it temporarily. This is a deliberate chain- or subnet-level switch, not a problem with your arguments. use the supported alternative call if one exists (the error name usually points at it), or wait for the feature to be enabled. ## Remediation [#remediation] This call or feature is switched off on this network ## Chain errors [#chain-errors] The exact chain error names (from the extrinsic receipt) that classify to `disabled`; the description says what triggered the failure and where to check. Each name has its own page: | Chain error | Description | | ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [`CallDisabled`](/docs/errors/chain/CallDisabled) | The extrinsic has been switched off in the current runtime and cannot be dispatched. There is no active raise site in current code; if seen, check release notes for whether the call was re-enabled in a newer runtime version. | | [`CommitRevealDisabled`](/docs/errors/chain/CommitRevealDisabled) | A weight commit or reveal was submitted on a subnet where commit-reveal is turned off. Check the `commit_reveal_weights_enabled` hyperparameter for the netuid (`btcli sudo get --netuid `); use plain `set_weights` instead when it is disabled. | | [`CommitRevealEnabled`](/docs/errors/chain/CommitRevealEnabled) | Plain `set_weights` was called on a subnet where commit-reveal is enabled, which requires the commit/reveal flow instead. Check the `commit_reveal_weights_enabled` hyperparameter for the netuid and switch to `commit_weights`/`reveal_weights`. | | [`Deprecated`](/docs/errors/chain/Deprecated) | The extrinsic has been removed and always fails, e.g. `schedule_swap_coldkey`, the swap pallet's user-liquidity calls, or `sudo_set_total_issuance`. Migrate to the replacement call noted in the deprecation (for coldkey swaps, `announce_coldkey_swap` plus `coldkey_swap`). | | [`DisabledTemporarily`](/docs/errors/chain/DisabledTemporarily) | The operation has been temporarily switched off in the runtime, usually as a hotfix measure. There is no active raise site in current code; if encountered, check the runtime version and release notes for when the feature is re-enabled. | | [`DynamicTempoBlockedByCommitReveal`](/docs/errors/chain/DynamicTempoBlockedByCommitReveal) | `trigger_epoch` is refused while commit-reveal is enabled on the subnet, because an out-of-band epoch would desync the CRv3 reveal window from the Drand schedule and drop committed weights. Check the `commit_reveal_weights_enabled` hyperparameter; disable it before manually triggering epochs. | | [`FaucetDisabled`](/docs/errors/chain/FaucetDisabled) | The `faucet` extrinsic was called on a runtime built without the pow-faucet feature, i.e. any real network. The faucet only works on local test chains compiled with that feature; use a funded wallet or testnet TAO instead. | | [`IssuanceDeactivated`](/docs/errors/chain/IssuanceDeactivated) | Total issuance cannot be adjusted because issuance has already been deactivated. Check the Balances `InactiveIssuance` state before calling `force_adjust_total_issuance` again. | | [`LimitOrdersDisabled`](/docs/errors/chain/LimitOrdersDisabled) | Order execution was attempted while the pallet's global switch is off. Check the `LimitOrdersEnabled` storage value; root must call `set_pallet_status` with true to enable the pallet. | | [`LiquidAlphaDisabled`](/docs/errors/chain/LiquidAlphaDisabled) | Setting `alpha_low`/`alpha_high` was attempted while liquid alpha is disabled on the subnet. Check the `LiquidAlphaOn` hyperparameter (`btcli sudo get --netuid `) and have the subnet owner enable liquid alpha first. | | [`NoChainExtension`](/docs/errors/chain/NoChainExtension) | The contract invoked `call_chain_extension` but this runtime registers no chain extension; such code is normally rejected at upload. Check that the target chain provides the chain extension the contract was built against. | | [`NotConfigured`](/docs/errors/chain/NotConfigured) | The permissionless safe-mode operation is disabled because its config option is `None`: `EnterDepositAmount` for `enter`, `ExtendDepositAmount` for `extend`, or `ReleaseDelay` for `release_deposit`. Check the runtime config or use the root-only force variants. | | [`POWRegistrationDisabled`](/docs/errors/chain/POWRegistrationDisabled) | `sudo_set_network_pow_registration_allowed` unconditionally fails because proof-of-work registration is deprecated and its toggle can no longer be changed. Nothing to check; the call is permanently disabled. | | [`PartialFillsNotEnabled`](/docs/errors/chain/PartialFillsNotEnabled) | A `partial_fill` amount was supplied for an order whose signed payload has `partial_fills_enabled` set to false. Check that field in the order payload; partial execution requires the signer to have opted in when signing. | | [`SubNetRegistrationDisabled`](/docs/errors/chain/SubNetRegistrationDisabled) | Neuron registration is switched off: either the subnet's `NetworkRegistrationAllowed` flag is false, or network creation has not opened yet (`NetworkRegistrationStartBlock` is in the future). Check the network\_registration\_allowed hyperparameter for the netuid. | | [`TransferDisallowed`](/docs/errors/chain/TransferDisallowed) | A stake transfer or cross-subnet move was attempted while the origin or destination subnet has stake transfers switched off. Check the `TransferToggle` storage for both netuids involved; the subnet owner must enable transfers first. | | [`VotingPowerTrackingNotEnabled`](/docs/errors/chain/VotingPowerTrackingNotEnabled) | Disabling voting power tracking was requested on a subnet where tracking is not currently active. Check the `VotingPowerTrackingEnabled` storage flag for the netuid before calling the disable extrinsic. | The same explanation is available in the terminal: `btcli explain disabled` (or `btcli explain ` for one exact chain error).