Troubleshooting
Diagnose common Vela Pro integration issues using console diagnostics, symptom descriptions, and targeted fixes.
Check the browser developer console first when diagnosing an integration issue. Vela Pro prefixes console warnings and errors with [vela-pro], while Vela's open-source core (@luxalgo/vela) uses [vela]. Console messages quoted below use representative symbol and provider names.
Installation and initialization
Vela Pro features do not appear on the chart
enableVelaPro() ran after VelaWorkspace was constructed. Because VelaWorkspace reads the plugin SDK registries at construction time, call enableVelaPro() once before the first new VelaWorkspace(...) call, typically at module scope in your application entry file rather than inside a component mount effect.
Features are still missing despite correct initialization order
Your application resolves two copies of @luxalgo/vela, so enableVelaPro() registers features into one instance while VelaWorkspace reads from the other without throwing an error. Run npm ls @luxalgo/vela in your application and verify that only a single version is resolved. See Installation for steps to deduplicate packages.
enableVelaPro() throws a missing SDK surface error
Console error: [vela-pro] the installed @luxalgo/vela build lacks the "registerChartType" SDK surface — upgrade @luxalgo/vela to a version compatible with this vela-pro release.
Vela Pro verifies that the core exports registerChartType, registerRendererLayer, and registerIcon before registering features. This error means the resolved @luxalgo/vela package is older than the minimum version required by your Vela Pro release. Check compatible versions in Upgrading.
Options passed to a second enableVelaPro() call are ignored
Each feature and module installs once per page lifecycle. Subsequent calls to enableVelaPro() cannot reconfigure features installed by the first call, and only watermark is re-evaluated. Pass all configuration options in a single enableVelaPro() call at startup. See Configuration precedence.
Data providers
The chart stays empty
When no registered provider serves the requested symbol, the workspace displays No registered provider serves "AAPL" (registered: binance) and the chart emits data:unresolved. Data loading waits until a matching provider is registered, so verify the symbol name and your providers option. When a provider matches the symbol but returns zero bars, the chart emits load:end with bars: 0, indicating an empty response from your provider's getBars implementation.
Footprint chart type renders no cells
Console warning: [vela-pro] provider "binance" serves no footprints for "BTCUSDT".
Footprint charts require a provider implementing all three FootprintFeed methods (getFootprints, subscribeFootprints, and footprintCaps). Standard candle-only providers such as the core's BinanceProvider do not serve footprint slices. See Footprint data for the feed interface. TPO charts require standard candles only and work with any provider.
Order-flow indicators are missing from the indicator menu
The indicator menu lists order-flow indicators only when the active symbol's provider implements FootprintFeed. If you add an order-flow indicator programmatically on a symbol without footprint support, the indicator plots nothing and logs a warning such as [vela-pro] Session Volume Profile needs a footprint-capable provider.
An order-flow indicator is empty on a monthly chart
Volume Delta, CVD, trade count indicators, and Bar Stats aggregate slices across a fixed bar duration, which calendar months do not have. On monthly timeframes (M, 3M), these indicators stay empty by design and log a warning starting with [vela-pro] this indicator needs a footprint-capable provider. Switch to a weekly or shorter timeframe.
Order book displays "No order book"
When the provider serving the active symbol does not implement subscribeBook, the panel displays BTCUSDT has no order book on its data source. Similarly, the Trades view displays No trades feed when subscribeTrades is missing. Implement DepthFeed on your provider (see Quotes and market depth), or disable the panel with orderBook: false.
Indicators and scripting
A Pine Script® indicator fails and renders nothing
In the Pine code editor, a failed run places an error marker in the editor and appends an entry to the logs strip. From application code, listen for indicator:error on the chart or error on the IndicatorHandle. If the console logs a message starting with [vela] no scripting engine registered for language "pine", the default Pine Script® engine is disabled. Remove pineEngine: false, or register a custom engine as shown in Custom runtimes.
A script with an import statement fails to run
The Pine Script® engine does not fetch external libraries automatically, so any script containing an import statement fails unless importResolver is configured on pineEngine. When using pineLibraryResolver({ url }), an HTTP 404 response reports the library as unknown and fails compilation with an error naming the import, while any other failed HTTP status throws Pine library "acme/levels/2" could not be loaded (HTTP 500). See Pine Script® with PineTS.
Scripts fail to compute under a Content-Security-Policy
By default, both the Pine Script® engine and the Pine code editor spawn Web Workers from blob: URLs, which are blocked when your Content-Security-Policy omits worker-src blob:. Either allow worker-src blob: in your policy, or run the Pine Script® engine on the main thread without a worker:
import { enableVelaPro } from '@luxalgo/vela-pro';
enableVelaPro({ pineEngine: { engine: 'inprocess' } });Although both the engine and the code editor accept a workerUrl option for self-hosted workers, neither package ships a standalone worker bundle, so use worker-src blob: or main-thread execution (engine: 'inprocess', disabling the editor via codeEditor: false if blob: workers cannot be allowed).
codeEditor() returns null or throws
codeEditor() returns null when the code editor is disabled (codeEditor: false) or before a workspace has been constructed. On pages with multiple workspaces, calling codeEditor() without an argument throws [vela-pro] 2 code editors are mounted — pass the widget or workspace to codeEditor(host). Pass the target workspace explicitly via codeEditor(workspace).
Modules
A module is skipped due to a missing dependency
Console error: [vela-pro] "journal" needs "trading", which is not installed.
A module whose prerequisite is missing is skipped during installation. Include the required module in the plugins array alongside it (note that the CLI command mentioned at the end of that console message does not apply when working from a clone):
import { enableVelaPro } from '@luxalgo/vela-pro';
import { trading } from '@luxalgo/vela-pro-trading';
import { journal } from '@luxalgo/vela-pro-journal';
enableVelaPro({ plugins: [trading(), journal()] });Listing the same module twice logs [vela-pro] "trading" is listed twice; the first one is kept.
A module's panel button is missing
Check the following causes in order:
- The module option is set to
falseinenableVelaPro(). enableVelaPro()ran afterVelaWorkspacewas constructed.- The console contains the missing-dependency error shown above.
- You supplied a custom
sidebarortopbararray on the workspace. Explicit toolbar lists replace the defaults, so contributed entries appear only if named directly or included via the'panels'or'actions'slot.
On mobile layouts, the side rail is hidden and panel toggles move into the overflow (...) menu.
A module controller such as tradingController() returns null for the same reasons when the module is disabled, skipped due to a missing prerequisite, or accessed before enableVelaPro() runs.
Standalone widgets do not render or update
Standalone widgets size themselves from their parent box, so mount el inside an explicitly sized container or flex cell. Widget menus and dialogs render without theme variables until you call ensureUIHost(host, theme) once on the mount root. Without controller.notePrice(...) on each incoming bar or tick, paper trading orders do not fill and alerts do not trigger. See Standalone widgets for complete wiring examples.
Persistence
Workspace state is not restored after a reload
VelaWorkspace does not persist state until you configure persist. Passing persist: true writes the workspace state document to localStorage under vela-workspace, while storage routes persistence to a custom adapter. When storage is asynchronous, the saved state is applied after its promise resolves following the initial paint. See Persistence for what each feature and module persists independently.
Constructor options appear ignored
Saved state overrides initial constructor defaults. When persist is enabled and a saved state document exists, the symbol, timeframe, layout, and user-modified module settings are restored from storage rather than constructor options. To verify, load the page temporarily with a fresh persist key; if your option takes effect, saved state was overriding it. See Configuration precedence for the full precedence order.
Two workspaces display each other's drawings
Per-symbol drawings are keyed by chart identifier and symbol. By default, a chart identifier combines the nearest ancestor DOM id on the workspace container (or shell when no ancestor has an id) with the cell ID, so two workspaces mounted in containers without distinct id attributes resolve to the same storage key. Assign a unique id to each container element, or customize keys via symbolDrawings: { chartKey }. The same option separates multiple tabs or named layouts on a single workspace; see Upgrading for an example.
Mobile layout
Workspace does not switch to mobile layout
Responsive layout breakpoints measure the VelaWorkspace container width rather than the browser viewport. Mobile layout activates when the container is narrower than approximately 640px, or approximately 920px on coarse-pointer touch devices such as tablets. Resize the container element, or lock the layout mode with layoutMode: 'mobile' or layoutMode: 'desktop' on VelaWorkspace. See Responsive layout.
Support
Email support@luxalgo.com with the following details:
- Resolved package versions in your application and the release tag checked out in your Vela Pro clone (using the commands below).
- Relevant browser console output, including all
[vela-pro]and[vela]messages. - A minimal reproduction built from the Quickstart setup so it runs without private market data feeds.
- Browser name and version, and whether the issue occurs on desktop layout, mobile layout, or both.
Run the first command in your application directory and the second inside your Vela Pro clone:
npm ls @luxalgo/vela @luxalgo/vela-ui @luxalgo/vela-pinets pinets
git describe --tags