Fix common issues fast

This typically means the terminal cannot retrieve data for the selected symbol and timeframe. Work through these checks in order:

• Check provider connection: Go to Settings → Data Providers and confirm your active provider shows a green connected status. Click Reconnect if it shows disconnected.
• Verify internet connection: Open a browser and confirm you can load any website. If not, the issue is your network, not the terminal.
• Check symbol and provider coverage: Not all providers cover all symbols. A provider that covers equities may not cover futures or certain crypto pairs. Check your provider's coverage list from their documentation.
• Try a different timeframe: If the Daily chart loads but the 1-minute doesn't, the provider may only supply daily OHLCV. Switch to a timeframe the provider explicitly supports.
• Try a different symbol: If switching to a common symbol (like BTC/USDT or SPY) loads correctly, the issue is specific to the original symbol, not the feed.

If the chart loads but prices look off, or candles seem out of sequence:

• Verify exchange and symbol: Some symbols trade on multiple exchanges at different prices (e.g., BTC/USDT on Binance vs. Bybit). Check that the exchange shown in the Data Strip matches where you're trading.
• Check live vs. cached status: Look at the Data Strip at the top of the chart. If it shows CACHED rather than LIVE, you're looking at stale data. Reconnect the feed first.
• Check the timeframe: Confirm the selected timeframe in the toolbar matches what you expect. It's easy to accidentally switch to a different timeframe when clicking around the toolbar.
• Clear chart cache: Go to Settings → Data → Clear Chart Cache for this symbol, then reload. Corrupted cache can cause visual inconsistencies.

Orderflow data (delta, bid/ask depth, footprint) requires Level 2 or tick-level data from your provider. This is a more expensive and specialized feed than standard OHLCV data.

• Check provider capabilities: Go to Settings → Data Providers, select your active provider, and check the "Supported data types" section. If Level 2 / tick data is not listed, that provider does not support orderflow for this instrument.
• Consider a provider upgrade: Some providers offer OHLCV on their standard tier and tick data on a higher tier. Check your provider's plan details.
• Futures and crypto have best coverage: Orderflow data is most commonly available for exchange-traded futures and major crypto pairs. Orderflow data for equities and forex is rarer and depends on the provider.

Quant Brain needs a minimum number of completed bars to calculate its readings. If the chart has only just loaded or you've switched to a symbol with limited history, Quant Brain will show Unavailable until enough bars have accumulated.

• Wait for more bars: On lower timeframes (1m, 5m), the required bars load within a few minutes of keeping the chart open. Quant Brain readings will populate automatically as bars complete.
• Check the specific reading: Some readings (like Delta Context) also require tick data from the provider. See "Orderflow panels show no data" above if those specific readings are unavailable.
• Try a higher timeframe temporarily: Switch to the 1H or 4H chart — there will be more historical bars available, and all Quant Brain readings should populate. Once confirmed working there, switch back to your preferred timeframe.

ORACLE connects to whichever AI provider is currently active. The fix depends on which provider you're using:

• For remote AI providers: Go to Settings → AI and check the provider status. A red indicator means the connection has failed. Verify your internet connection, check if the provider has a status page showing any outages, and re-enter your API key if prompted.
• For local AI (Ollama or built-in): Go to Settings → AI → Local Models and click Restart LLM Service. Wait 10–15 seconds for the service to reinitialize, then try ORACLE again.
• Check the active model: Confirm a model is actually set as active in the model list. If no model is active and you're using local AI, ORACLE has nothing to respond with.

Slow responses from local models are usually a hardware mismatch — the model is larger than your available CPU/GPU resources can comfortably handle.

• Switch to a smaller model: The 0.5B model is optimized for CPU and produces responses in 2–5 seconds on most machines. If responses are taking more than 30 seconds, the active model is too large for your hardware.
• Enable GPU acceleration: Go to Settings → AI → Performance and enable GPU mode if you have a compatible GPU. Even older GPUs can dramatically accelerate local model inference.
• Close other applications: If RAM is being used by browsers, video players, or other applications, the model may be partially paged to slower storage. Close what you don't need and try again.
• Restart LLM service: A service that has been running for a long time can degrade. Restart it from Settings → AI → Local Models → Restart LLM Service.

ORACLE reads terminal context automatically — but only if that context is available. If ORACLE's responses feel generic, one of these is usually the cause:

• Load a chart first: ORACLE reads the active chart. If no chart is loaded (the workspace is empty), ORACLE has no market context. Load a symbol and timeframe before asking market questions.
• Open the Quant Brain panel: ORACLE reads the Quant Brain panel's current state. If the panel is closed, that context is not included. Open it from the sidebar.
• Check context routing: Go to Settings → AI → Privacy and check which context categories are enabled for your active AI provider. If journal context is disabled, ORACLE won't reference your trade history.
• Be more specific in your question: Vague questions produce vague answers even with full context. Compare "What should I do?" (generic) with "Given the current Quant Brain readings and my last 5 journal entries, does my planned long setup still make sense?" (specific).

A stuck download is almost always one of two things: not enough disk space, or an internet interruption mid-download.

• Check available disk space: Model files range from 350MB to 8GB. Ensure you have at least 2× the model size free on the drive where Dome Terminal stores models (shown in Settings → AI → Storage).
• Verify internet connection: Downloads pause automatically if the connection drops. Resume the download from Settings → AI → Local Models — incomplete downloads resume from where they left off.
• Cancel and restart: If the progress bar hasn't moved in more than 5 minutes, cancel the download and start it again. The terminal will resume from the last completed chunk.
• Check for antivirus interference: Some antivirus programs scan large downloads in real-time, which can cause apparent stalls. If the download consistently sticks at a specific percentage, temporarily pause your antivirus and try again.

A blocked action is logged with a specific reason. The first step is always to check the bot log — do not guess.

• Check Bot → Logs: Every blocked action is logged with the exact reason. Open Bot Management → [Bot Name] → Logs and find the blocked entry. The reason field tells you exactly which gate fired.
• Kill switch active: If the manual kill switch was engaged (from the toolbar or a shortcut), the bot will not execute until you manually re-enable it. Check the bot status indicator in Bot Management.
• Daily loss limit reached: If the bot's daily loss gate has been hit, it is paused until midnight. Review the daily PnL in the log and wait for the next session, or adjust the limit in bot settings if you believe it's misconfigured.
• Paper mode active when live was expected: Confirm the bot mode in the bot configuration panel. If it shows PAPER, the bot is simulating — no real orders will be placed regardless of how the strategy fires.
• Strategy script failing validation: If the underlying script has been updated but not re-validated, the bot may pause. Go to Script Library, re-validate the script, and resume the bot.

If the bot status shows Active but no entries are being generated, the strategy conditions are likely not being met — or the bot configuration needs checking.

• Verify bot state is Active: Green indicator = Active. Yellow = Paused. Grey = Inactive. A paused or inactive bot does not execute even when conditions are met.
• Check the scheduling settings: Some bots are configured to only run during specific session hours. If the current time is outside the configured trading hours, the bot will not trigger. Check Bot Settings → Schedule.
• Confirm strategy conditions on the chart: Open the script in Script Library and check what conditions need to be true for an entry signal. Then look at the live chart — are those conditions currently being met? If the market has been in a regime the strategy doesn't trade (e.g., a trend strategy in a ranging market), no signals is correct behavior.
• Check the symbol and timeframe: Confirm the bot is watching the same symbol and timeframe the strategy was designed and validated for.

Paper mode replicates the strategy logic against live data but simulates execution — this introduces differences that are expected and by design.

• Fill assumptions differ from live: Paper mode assumes fills at the signal price (or with a small slippage estimate). In live trading, actual fills depend on liquidity, queue position, and market conditions. Paper mode results are optimistic about fill quality — this is expected.
• This is why you review paper logs before going live: If paper results look good, they don't guarantee live results will match. The purpose of the paper period is to verify that the strategy logic fires correctly and at the right times — not to predict exact live profitability.
• Slippage settings: You can make paper mode more conservative by increasing the slippage assumption in Bot Settings → Execution → Simulated Slippage. A higher simulated slippage gives a more conservative paper performance estimate.

Settings are organized into seven primary categories. If you're not sure which one to check, use the search bar at the top of the Settings panel (press Ctrl+, to open Settings, then type the setting name).

• Data: Provider connections, data refresh rates, cache settings, historical data
• Chart: Chart types, default timeframe, indicator defaults, drawing tool persistence, color themes
• Risk: Account risk limits, daily loss gate defaults, position size limits, kill switch configuration
• AI: Provider selection, local model management, privacy/context controls, Ollama configuration
• Journal: Default fields, tagging system, ORACLE journal access, export settings
• Alerts: Alert delivery (in-app, email, sound), system alerts (feed status), alert history
• Advanced: Keyboard shortcuts, performance settings, beta features, storage management

Risk limit changes apply immediately to new trades and new bot sessions — they do not retroactively modify active positions or currently-running bots.

• New trades: Any manual trade or bot-initiated order placed after you saved the new settings will use the updated limits.
• Currently active positions: An open position entered before the settings change is not affected. The new limits apply from the next entry forward.
• Running bots: A bot that is currently Active was launched with the risk settings that were active at that time. To apply new risk settings to a running bot, pause it, update the bot's own risk gate configuration, and resume it.
• Global vs. bot-level limits: There are two layers of risk limits — the global account limits in Settings → Risk, and the per-bot risk gate settings in each bot's configuration. Both must be consistent for the behavior you want.

Password reset is available on the login screen and does not require contacting support:

• On the Dome Terminal login page, click Forgot Password below the login form.
• Enter the email address associated with your account and click Send Reset Link.
• Check your inbox (and spam folder) for an email from noreply@dometerminal.com. The reset link is valid for 60 minutes.
• If you don't receive the email within 5 minutes or the link has expired, contact support@dometerminal.com with your account email address.