Troubleshooting

Identify the route, token network/address, session or strategy, selected account/mode, and approximate time before retrying.

A button or setting is missing

In desktop Terminal, hover over or click the top-right avatar and choose Settings; clicking keeps the menu open, while the account summary at the top of the menu opens your page. Click the avatar again, press Escape, or click outside to dismiss it. On mobile, use Open menu → Settings and scroll the tabs. The current labels are Plan, Wallets, AI connections and Bug reports. Hidden Brokerages or Paper accounts tabs are not an instruction to connect a broker: use Wallets → Trading mode for Paper.

Wrong balance or missing activity

Check Paper cash versus Cash, the selected account/network and the time of the snapshot. Portfolio value includes holdings and cash your strategies have not spent; available cash can exclude strategy allocations, order reservations and pending deposits. If money seems missing after deploying a Real-money strategy, open the Cash menu: it lists what is In strategies. In Positions & Orders, check the account and order view, then Load older orders when offered. A new chat still belongs to the same account.

If a holding lacks a price or verified entry cost, the Terminal portfolio header keeps the known value visible; P/L excludes holdings without both inputs, and stays — if none can be evaluated. Hover over the portfolio control for exclusion counts and the partial-total explanation; the amounts have no visible Partial tags. Open the control to inspect Positions & Orders. A missing price is not proof a token is worth zero. See Partial portfolio value and P/L. Account-verification or balance-read failures can still make the header unavailable.

Funding is pending

Check deposit status and withdrawal confirmation. Pending on-chain funds and tradable funds can differ. Confirming an address does not submit the transfer. A subscription payment does not fund the wallet.

An action's outcome is uncertain

An interrupted chat, closed dialog or timed-out request is not proof that the action never happened. Inspect the saved record, order, transfer or deployment before making another request. Use the original flow's same-attempt retry when offered; do not create duplicate transactions to diagnose a delayed response.

A strategy will not stop immediately

Liquidate & Stop stays deployed until strategy-owned positions are confirmed flat. Inspect exit progress, orders and any blocked/failed state. Switching to Paper, signing out or deleting a bookmark does not stop real activity. See Stopping strategies.

On an Astral Wallet (Solana) deployment, a token that can't be sold no longer blocks the stop: when no supported route can sell it, or the whole position is worth less than the minimum trading fee, the stop leaves the token in your wallet and finishes. See When a wallet token can't be sold.

If you already sold directly at a legacy broker and the paused/liquidating deployment remains, use the eligible stop dialog's I already sold this position at my broker → Verify external close & undeploy recovery. Astral must verify flatness and no pending orders; this does not submit another sale. See External-close recovery.

A Kraken exit is below the minimum order size

Check whether the exit is a full-position close or a partial sell sized from strategy equity. For eligible existing funded Kraken deployments, the October 20 production hotfix can release verified USD crypto dust worth at most $0.10 after an actual full-close exit fill. The coin stays in the broker account. Larger or unverified remainders remain blocked. See Full-position exits and Kraken dust for the conditions.

If you already sold directly at Kraken, use the external-close recovery above. Astral must verify zero holdings and no working orders for the affected position. Missing sale prices and fees leave final profit and returns unavailable; a reported manual sale does not supply those details.

Token or chart unavailable

Check the exact address, network and supported interval. Discovery and chart coverage can differ. New tokens may have little or no usable history. Missing data is not zero; inspect Markets and the source status.

Backtest has fewer bars or no trades

Read the effective window, loaded history and warmup. Confirm the conditions actually became true and that sizing and costs permit the simulated action. Do not infer the execution period from the date picker alone.

A verified feed range can contain no price observations for a particular token. Ask for that exact asset's history and original scheduled interval; do not replace the cohort or choose different dates merely to hide the refusal. See Backtesting.

History is busy or accounting disagrees

Temporary history overload has a bounded retry window. After it ends, wait briefly before retrying unchanged. Missing certification or unqualified launch facts need a data repair, not repeated requests. An execution-ledger mismatch needs a platform report with the original run reference; do not edit sizing, costs or tolerances to hide it. See Service and accounting failures.

Chat chart context or result table is inconsistent

If chart-context synchronization fails with an out-of-date notice, copy the draft, reload that chat and check its token and interval before sending. If a completed table reports missing cells, ask for the exact stored result; unavailable values are not zero. A stopped or reconnected conversation does not prove that prior effects were undone. See Terminal recovery.

Chat says product agent access is paused

The product can allow monitoring while refusing new agent turns, because an agent can submit execution requests. An explicit pause rejection should stop the chat's loading state and explain that access is paused; that attempt was refused rather than queued for later agent processing. Keep a copy of the message and retry only when access is restored. Changing product, subscribing or switching Paper / Real money mode does not bypass the pause, stop existing strategies or undo earlier actions. Use the original product's monitoring/cancel/close controls for existing execution. See Product access and switching.

Wallet access unavailable

Confirm the current Astral session and use the available retry/sign-in flow. Wallet functionality must be enabled and configured for the release. A subscription cannot unlock an unavailable wallet path. See Wallets.

Transaction status is unclear

Inspect account activity and any transaction link before submitting again. A delayed or failed response may follow a successful submission. Do not duplicate the transaction merely because the interface has not updated.

Strategy is not operating

Check mode, active/paused status, permissions, token support, account availability and the latest event. Paper events and live transactions are different. Review the error before resuming or redeploying.

In the strategy's Live view, compare its last price bar with the current time. If it is well behind, or warmup stays at the same bar count such as 0 / 26 bars, live data for that strategy has stopped. The strategy cannot finish warmup or evaluate a new signal until data resumes. Do not redeploy to diagnose it; report the strategy and the last price bar time shown. Ask the assistant why the strategy hasn't traded to see the same warmup, last-bar and health details.

For a real Solana wallet strategy, warmup completion and allocated cash do not prove that a triggered trade was submitted. Active · trading blocked can identify a wallet token balance verification failure: Astral needs a verified balance record even when you have never owned the token. You do not need to buy it manually. The platform prepares missing records before eligible fresh signals; canceled or expired signals are not replayed. A successfully admitted trade clears this warning while other readiness checks remain. See Solana token balance checks.

If an older release keeps reporting ready despite missing trades, report the strategy, token address/network, approximate signal time and visible status. Do not change allocations, bypass a pause or repeatedly redeploy to diagnose it. The same recovery boundary applies on desktop and mobile web; a source fix does not confirm that your running release includes it.

Billing or feature access differs

Review current access in Settings and the billing portal. Distinguish account limits from unsupported token operations. Contact support if the displayed subscription and access disagree.

Contact support

Use Help. Include the action, expected/actual result, visible error and approximate time. Never send private keys, passwords, one-time codes or payment-card details.