Configuration
Logs & Debugging
Last updated March 1, 2026
Every strategy run generates log entries. The Logs tab lets you filter and inspect them in real time, essential for understanding why your strategy is or isn't trading.
Reading Logs
Log Levels
| Level | When it appears |
|---|---|
info | Normal execution events: run started, buy/sell executed, run finished. |
warn | Non-fatal issues: buy/sell skipped (no price, no position, invalid amount), run skipped (trade hours, weekend, over daily limit). |
error | Fatal strategy errors: exceptions thrown by the compiled code, strategy timeout, DB errors. |
Filters & Search
The Logs tab supports filtering by: log level (info / warn / error / all), symbol, run ID, and free-text search. Run IDs are useful for tracing all events from a single execution cycle.
Each log entry has a meta JSON payload. For buy/sell events this includes price, quantity, USD amount, and position ID. You can inspect meta by expanding the log row.
Advanced Logging
Enable Advanced Logging in Settings to get a pre-run snapshot on every tick. Each snapshot includes:
- Current mark price for the symbol
- Whether a position is currently open
- Entry price and entry time (if in position)
- Unrealized PnL % (if in position)
- Run ID for cross-referencing other log entries from the same tick
Warning: Advanced Logging significantly increases log volume. For a project running every 5 minutes across 2 symbols, this adds ~576 extra log entries per day. Use it for debugging, then disable it once your strategy is verified.
Common Errors
| Error message | Cause | Fix |
|---|---|---|
Legacy hp_trade_buy block detected | Old BUY block from an older workspace version. | Delete the old block and drag a new BUY block from the Trading category. |
No generated_js found. Skipping run. | The project has no compiled code. | Open the Editor and click Compile before running. |
BUY skipped: no price available | The kline cache has no data for this symbol/timeframe yet. | Wait for the kline manager to populate data. Check that your deployment has the symbol configured. |
SELL skipped: no open position | Your strategy tried to sell when there was nothing to sell. | Add an In Position check before your sell block. |
Run skipped: outside trade hours | The current UTC time is outside your configured trade window. | Adjust trade hours in Settings, or disable the window to trade 24/7. |
Strategy error: Script execution timed out | The compiled strategy took more than 5 seconds to run. | Simplify your strategy. Reduce the number of indicator blocks or avoid deeply nested logic. |
| Indicators returning NaN | Not enough historical bars in the cache to compute the indicator (e.g. EMA 200 needs 200 bars). | Wait for the cache to populate more history, or reduce indicator periods. |