Documentation
Troubleshooting
Start by identifying the affected route, active session, symbol, strategy, account, and approximate time. Then separate display or connection state from broker, market-data, feature-access, or authorization state.
Terminal and charts
If the page fails with AbortSignal.timeout is not a function, reload after the updated Classic web release is available. The compatibility repair keeps request deadlines and cancellation active on browsers missing that helper; it does not change trading or account state. If the error persists, update the browser and include its version and device in your report. Installed apps can require their own release update.
A session or panel looks emptyRestore the intended session before assuming data is missing.
Wait for session restoration and panel hydration, then refresh once. Confirm you opened the intended session. Broker, watchlist, and strategy panels can load after the base Terminal route.
A shortcut does not workKeyboard focus controls whether app shortcuts run.
Click the Terminal or active chart and retry. Shortcuts are ignored while focus is in an input, textarea, select, editable field, or some open dialogs. See Shortcuts.
Mobile looks different from desktopMobile uses dedicated navigation and panel drawers.
Mobile uses bottom navigation and dedicated drawers for core app and trading panels. Multi-chart, detailed analysis, and simultaneous side-by-side work remain denser on desktop.
Strategies and backtests
A backtest fails validationStart with the displayed validation category and message.
Read the displayed category and message, then check asset symbols, bar size, function signatures, conditions, sizing, and data availability. Ask Astral to revise the failing specification.
A forex or metals backtest says price history could not be verifiedThe named bar has no quotes that establish its price.
The message names the symbol, bar size and bar time whose provider quotes could not establish a price. Choose a date range that excludes that bar. If it says to try again shortly, the quote provider was unavailable; retry the same run later. Fees and cost settings do not affect this check. When a bar can be rebuilt from its quotes instead, the backtest runs and shows a bars rebuilt from quotes note. See Forex and metals price checks.
A deployment is not producing activityA quiet deployment may be valid if its rule has not fired.
Confirm its execution mode, active or paused state, strategy timeframe, notification channels, paper account and allocation or broker account, and whether the rule actually fired. Notifications-only deployments do not produce a tracked paper portfolio.
Deploy stays unavailable in Paper modeThe line under Deploy names the missing requirement.
Paper deployment needs a paper account and a Strategy Allocation no larger than that account's unassigned cash. Read the line beneath Deploy: choose or create a paper account, enter an allocation, pick an account that still has unassigned cash, or wait for the balance to load. If Deploy opens a plan prompt, your plan's Paper deployment limit is reached. See Deploy with Astral Paper.
Classic order recovery
An order-recovery status alone cannot tell you whether a fill is missing: it neither proves nor rules one out. Check the recorded orders, executions and recovery result; restored prices or flat displayed holdings cannot settle it.
For recovering order history or order history recovery incomplete, see Saved & Deployed Strategies. A flat Paper deployment can need replay even without holdings. A recovered price feed does not establish that order replay or accounting checks have completed. When replay completes, its recovery status clears even if the deployment remains paused. A deliberate Pause and any remaining accounting or protection checks still apply; replay completion does not resume trading.
A rejected close is not a missing fill: its requested quantity or direction did not match the holdings available after existing reservations. Avoid repeated submissions or guessing a new quantity. Include the strategy, symbol, time and displayed error in a support report so the recorded quantities can be checked.
Alerts and notifications
Check active state, timing, frequency, expiration, mute status, profile channels, verified destinations, browser permissions, and whether the condition occurred. An order event and a manual market alert are different sources.
Brokers and orders
Broker data differs from AstralTreat the broker as the account source of truth.
Verify the selected connection and account, refresh the account page, and check connection renewal. Use the broker as the source of truth for balances, positions, orders, fills, fees, buying power, and restrictions.
An order result is unclearCheck existing order state before submitting again.
Open Orders and the broker before retrying. Repeated submission can duplicate exposure. A preview is not a fill, and a cancellation can race with execution.
A deployment is pausedResolve the account condition before resuming.
Inspect the health or error message for rejection, insufficient funds, position-integrity mismatch, connection loss, or access change. Resolve the broker/account condition before resuming or redeploying.
Escalate with useful context
Use Help and include the route, session or strategy, symbol, non-sensitive broker/account identifier, action, expected result, actual result, visible error, and approximate time. Never send passwords, one-time codes, private keys, or full payment details.