How to Respond to Stale Market Data

Recognize the state Loading means the first request has not completed. Refreshing means the previous value remains while a newer request is checked. Stale means the latest confirmed result is being shown. Unavailable means the platform could not confirm usable data. These labels carry more information than a number by itself. A cached quote or old signal can still be useful for orientation, but it should not be treated as a current execution value. Run a bounded recovery Confirm the symbol, timeframe, session, and account context. Wait for the first snapshot, then use the affected card’s Retry or refresh control once. If only one symbol is affected, reselect a validated result and allow the new context to settle. If several cards are stale together, check the top-level connection and plan state before retrying each card. Repeated refreshes can make it harder to tell whether the newest request has completed. Do not fill in missing data Do not infer a daily percentage from the first candle in an arbitrary history window, use another account’s position, or treat a prior-session overlay as current. An empty or blank value can be safer than a plausible value with the wrong baseline. When a signal, chart, or account snapshot is unavailable, pause the action that depends on it. Review the situation again only after the relevant source confirms a usable result. Give support a useful report If the state remains after the checklist, open /help/tickets/new with the workspace, symbol, timeframe, account context without sensitive identifiers, visible state, approximate time, and what changed after one retry. This gives support a reproducible starting point. Never include passwords, access tokens, private keys, or full payment details. For Terminal-specific meanings and recovery, read /help/articles/terminal-user-manual.