Known issues

Known issues, workarounds, and fix timelines.

This page lists current known issues in Dome Terminal with their status, expected resolution, and any available workaround.

Dome Terminal follows a policy of honest reporting for known issues. A terminal that handles real market data, AI analysis, and automated strategies must be transparent about its current limitations.

Issues are categorized by severity: critical issues affect safety or data integrity, high issues affect core workflows, medium issues are significant but have workarounds, and low issues are minor cosmetic or edge-case behaviors.

Each entry includes the affected feature, a description of the behavior, any available workaround, the current status, and the target release for a fix where one is planned.

The list is updated with each release. Issues that are resolved in a release are moved to the changelog with their fix note.

  • Critical: issues affecting account safety, data integrity, or live execution accuracy are tracked and prioritized first.
  • High: issues affecting core charting, AI, script execution, or portfolio data with no straightforward workaround.
  • Medium: issues with available workarounds, including display inconsistencies and non-critical data delays.
  • Low: cosmetic, performance, or edge-case issues that do not affect trading decisions or data reliability.
  • Workarounds are documented where available so traders can continue working while a fix is prepared.
  • Status labels show whether an issue is confirmed, in progress, blocked, or awaiting release.
  • Community-reported issues are acknowledged and investigated before being added to this list.
  • Security-related issues are handled through the responsible disclosure process before public disclosure.

Current issue status

No critical issues are currently listed for the stable release.

The stable channel is considered suitable for normal trading workflow use. Issues in earlier builds are documented below for reference. A serious trader does not need a page that talks around the workflow; the section has to explain what changes in the moment before a decision, while the position is open, and after the outcome is recorded.

The practical value is in the connection between context and behavior. A chart level matters more when it is tied to invalidation, a bot setting matters more when the drawdown rule is visible, and an AI answer matters more when the source context can be reviewed.

Dome Terminal keeps that connection visible so the trader can work from evidence instead of mood. The product is built for the unglamorous parts of trading: waiting, sizing down, skipping weak setups, reviewing losses, and admitting when a backtest is too fragile.

That philosophy gives serious traders a calmer way to work. Instead of chasing scattered dashboards and generic chatbot answers, the trader can ask better questions from inside the exact context where the decision is being made.

  • Local LLM Lab model loading may be slow on first launch after a system restart. Workaround: pre-warm the model from settings.
  • Python Lab output charts may not refresh automatically when switching between research notebooks. Workaround: manually refresh the output panel.
  • Market Intelligence news deduplication may show duplicate articles during rapid provider failover. Workaround: apply the topic filter to reduce repeated entries.
  • The journal export may include extra whitespace in CSV format for entries with multi-line notes. Workaround: open in Excel and apply trim formatting.
  • Bot scheduling in the early-AM session window may have a 30-second delay on first trigger. Workaround: configure triggers 60 seconds earlier than the intended window.
  • The Academy progress tracker may not reflect completed quiz scores until the next login. Workaround: log out and back in to refresh progress.
  • Orderflow delta accumulation may reset when the data provider reconnects after a brief interruption. Workaround: restart the orderflow panel to re-initialize the session accumulation.
  • The changelog page may show a loading state briefly on first visit before rendering the release list. Workaround: wait three to five seconds for the data layer to initialize.