Skip to content

Why an action is unavailable

You opened a screen and it told you the operation is not available in this build. Here is what that means.

The exact build you are running does not carry evidence for that operation, on that protocol, on that network. So the wallet refuses it up front, and names what is missing, rather than offering an action that would fail somewhere later.

The screen still loads. It does not disappear from navigation. That is deliberate: a feature that silently vanishes between builds leaves you unsure whether you imagined it.

  • Not an outage. Nothing is down. This is a property of your build.
  • Not a permission problem. There is no account, no tier, and no upgrade.
  • Not a setting. There is no toggle in the wallet that changes it.
  • Not a bug to report. It is the product working as designed. Reporting it is fine and the answer will be this page.
  • Reinstalling the extension.
  • Clearing storage or resetting the wallet.
  • Switching accounts, or importing the phrase again.
  • Switching networks, although a different network genuinely can have a different authorization state, because authorization is recorded per network.
  • Waiting. It changes when a new build is released carrying evidence for that operation, not before.

Screens fall into groups, recorded in the wallet’s generated route inventory:

GroupWhat it means
Always reachableNo protocol gate. Present in every build.
Gated and authorizedBehind a protocol gate that your release authorizes.
Gated and blockedBehind a protocol gate with no authorized operation. Fails closed.
Runtime gatedThe gate depends on what you navigated from.

In the 1.7.5.8 baseline, 69 of 113 routes are always reachable, 40 are gated and blocked, and 4 are runtime gated. Nothing is gated and authorized, because the baseline authorizes nothing.

Everything with no protocol gate: create and import wallets, receive, manage address types, switch networks, connect and disconnect sites, read activity, inspect a transaction by id, view locked coins and coin health, use the address book, and use the security dashboard.

There is nothing to configure locally. Follow the release list for a build that carries it, and read What this release authorizes for the current position.