Find the Last Working Send Stage
If Ledger Live Send is not working, name the first stage you cannot complete: selecting funds, validating the destination, connecting the signer, approving, or broadcasting. The current product is Ledger Wallet, formerly Ledger Live. A precise stage prevents treating a recipient-format error as Bluetooth failure or a network incident as a reason to reset hardware. Keep the displayed message and any transaction ID.
Stage One: Select Spendable Funds on the Right Chain
Check the actual asset and network in the sending account. A portfolio countervalue is not a spendable balance for a single transaction. Staking, account reserves, pending activity, and network fees can affect availability. Token transfers can require a separate native fee asset on that same chain. Similar tickers across networks do not make the balances interchangeable.
Compare the destination service’s deposit requirements with your selected route. Some assets or services require additional information such as a memo or tag. Use the current official asset and recipient instructions rather than guessing a value. Ledger’s send workflow reference is a starting point for reviewing the intended action.
Stage Two: Establish the Signer’s Identity and Connection
Unlock the Ledger directly and follow the requested blockchain-app prompt. For desktop, use USB with a data-capable cable; for supported mobile hardware, follow its documented connection method. Close competing wallet interfaces if the device appears busy. A previously loaded account page can remain visible without a live signing connection.
If the error says the device does not match, identify the initialized device configuration that controls that account. Do not erase the present wallet or repeatedly create new accounts as a matching experiment. App-lock access and hardware signing are also separate: opening the computer app does not authorize spending.
Stage Three: Review the Approval You Receive
Read the recipient, amount, and other displayed transaction information on the hardware. Reject unexpected requests, especially an unrelated contract approval introduced by someone offering troubleshooting help. If the requested device app is too old, consult Ledger’s app-update guidance. Host application, Ledger OS, and blockchain apps can have different update requirements.
Complete maintenance through the supported process before resuming the transfer. Never disconnect a progressing device OS installation merely to test whether Send now works. Connection and update troubleshooting should preserve the wallet configuration rather than introducing an unnecessary recovery operation.
Stage Four: Confirm Broadcast Before Another Attempt
After approval, inspect any transaction hash on the exact blockchain. A send error or app crash does not conclusively prove the transfer was absent. If the record succeeded, do not send again. If pending, investigate confirmations or supported replacement procedures. If no result appears, recheck network and sender history before assuming another payment is harmless.
Use Ledger’s incident page when fee estimation, broadcast, or account refresh fails. A provider incident and a USB failure require different fixes, so retain the stage distinction throughout the investigation.
Sending Questions
Will raising the fee fix every failure?
No. It cannot correct a missing signer, incorrect recipient format, wrong network, or contract condition. Understand the error before changing transaction parameters.
Does support need recovery words to enable Send?
No. Provide the network, message, failure stage, app version, and relevant public identifier only. Keep the recovery phrase private and never transfer funds to a troubleshooting assistant’s validation address.