Reference
Messages in the app
What the app's messages mean and what to do next.
The app turns wallet, network and program responses into one sentence. Details under a message shows the original text, and View transaction opens it on Solana Explorer when there is one.
Your wallet#
| Message | What to do |
|---|
| You declined the request in your wallet. | Nothing happened. Try again when ready. |
| Your wallet needs a little SOL for network fees. | Add SOL to the wallet. |
| Your wallet does not hold that much of this token. | Deposit less, or add the token to your wallet. |
Your vault#
| Message | What to do |
|---|
| Your vault does not hold enough for this. | Deposit more, or lower the amount. |
| Your vault is reserved by an active order. | Cancel the order, or wait for it to fill or expire. |
| Resume the saved transfer first | Resume it in the Vault panel; see Resume a saved transaction. |
The book#
| Message | What to do |
|---|
| A matching round took the book first, so your request was not sent. | Try again in a few seconds. |
| Another request reached the book first, so yours was not sent. | Try again. |
| All 16 book positions are taken. | Try again after an order fills, expires or is cancelled. |
| You already have an active order. | Cancel it before sealing another. |
| Your vault is still being registered with the matching network. | Wait until the ticket stops showing Registering your vault for matching. |
| Recovery opens ten minutes after the computation started. | Wait until the app offers recovery. |
| An order you signed on this device is still unresolved. | Use Finish the signed order saved on this device under Your order. |
The network#
| Message | What to do |
|---|
| The transaction expired before it was sent. | Try again; nothing was sent. |
| The network didn't confirm the transaction in time. | Resume it from the saved record in the Vault panel or under Your order. |
| Your session ended. Connect your wallet again. | Connect and sign in again; sessions last eight hours. |
| The network could not be reached. | Check your connection and try again. |