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
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 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 profile, paper capital or broker account, and whether the rule actually fired. Notifications-only deployments do not produce a tracked paper portfolio.
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.