One place for the data every test depends on.

Sources and synchronization

Each source represents a platform installation or connection with its own symbols, candles and configuration. Sync downloads candles per symbol and timeframe into the vault; the vault view shows the available range so date modes such as “days back from the last vault candle” resolve against real data.

Spread handling is per broker: use the automatic values captured from the platform, or set manual overrides per symbol when you want conservative assumptions. Symbol calibration tools help align broker-specific contract settings before exporting bots. Spreads are expressed in price units (the symbol quote), the same units the backtests apply. A sync also re-calibrates the symbol’s spread override from the ticks it downloaded unless you ask it not to: jobs run before and after a sync may therefore use a different spread.

All candle and trade timestamps in TR-GAB are the broker server’s time. Each broker exposes its offset from UTC (visible in the Brokers tab and returned by the MCP tools), so sessions defined in UTC can be translated before mining.

Syncing candles: what to expect

• Sync runs in the background. Press Sync and keep working: the panel shows progress per chunk and a Stop button; what was downloaded before a Stop is kept. Through MCP, sync_candles returns a job id and get_sync_status reports progress.
• Pick the timeframe. The default M1 sync derives the other timeframes from the minute candles. When a broker keeps only a few months of M1 (common on demo servers), choose H1, H4 or D1 directly: brokers usually serve years of those.
• The vault stores what the broker served. After a sync the panel says exactly which range arrived and, when the first candle is far later than requested, that the terminal had no older history: it is the broker’s depth, not a download error. Raising “Max bars” in the platform does not create history the server does not have.
• Deeper direct syncs survive. Re-syncing M1 rebuilds the derived timeframes only over the range the M1 candles cover; an H1 or H4 series synced directly with more history is not overwritten.
• The first request for a symbol the platform never opened can take a few seconds while the terminal downloads; the sync retries it automatically.
• One symbol per sync. The symbol box is the common broker selector (type to filter; every row shows the source and the vault range of the symbol, and the broker contract data when the source is a connected terminal). Pick a symbol, then Sync.

When a screen needs candles the vault does not have

Pattern Scanner and Marketing compute channels on closed candles of the channel timeframe. When the vault is short (an empty symbol, or a channel that needs more history than the vault holds, or a vault that is behind the current time), the screen asks the broker terminal for the missing stretch, behind and ahead, and stores it in the vault through the same path as a sync, so the next request is served from the vault. The request is capped by a number of days per timeframe (short on M1, long on D1) and the screen says what came from the vault, what came from the terminal and whether the total is still short (vault 0 D1 + terminal 40 D1 = 40 < 365 needed). A symbol the terminal offers but the vault never downloaded is listed as terminal only, no vault candles.

Reads never start a terminal: when the terminal of a source is closed, a data request answers that the terminal is not running instead of launching it, and the app tells you. Connecting to a source on purpose can launch it, and says so.

The default broker

The default broker (visible as a chip in the top bar, changeable from there or from Market Vault) is the ambient destination for platform actions across the product: row-level test buttons, workflow exports and bot downloads route to it unless a screen selects something else. Jobs and tests always record which source they used, so results remain attributable when you switch defaults.

Market calendar

The vault also manages the economic calendar used by Event Mining and by calendar-aware features. Install the calendar bridge, sync events, and the calendar status view shows the coverage you can mine against.