Activity Log
The Activity Log tab is a chronological timeline of everything the bot has done. Think of it as the bot’s diary.
What Gets Logged
Every significant action and event is recorded:
| Type | Color | What It Includes |
|---|---|---|
| BOT | Blue | Bot started, stopped, scan cycles completed |
| TRADE | Green | Positions opened, closed, orders submitted |
| RISK | Amber | Risk limit warnings, daily loss approached, safeguard triggered |
| EMERGENCY | Red | Kill switch activated, emergency close, system errors |
| SYSTEM | Gray | Connection events, reconnections, data updates |
Reading the Log
Each log entry shows:
- Timestamp — When it happened
- Type badge — Color-coded category (BOT, TRADE, RISK, EMERGENCY, SYSTEM)
- Message — Description of what happened
The log is presented as a collapsible panel. Click ”📋 ACTIVITY LOG” to expand it and see the entries.
Common Log Messages
Here are some messages you might see:
- “Bot started” — You or the system started the trading bot
- “Bot stopped” — The bot was paused
- “Scan cycle completed — no opportunities” — The bot checked the market but didn’t find anything matching your strategies
- “Position opened: SPX Iron Condor” — A new trade was entered
- “Position closed: profit target reached” — A position was closed at its profit target
- “Daily loss limit approached” — P&L is nearing your max daily loss
- “Kill switch activated” — All trading halted due to a risk event
- “API reconnected” — The broker connection was restored after a dropout
Clearing the Log
If the log gets too long, you can clear it:
- Click the “Clear All” button (trash icon) next to the activity log header
- A confirmation dialog appears warning that this will permanently delete all trades from the database and reset your P&L stats
- Click “Clear” to confirm, or “Cancel” to keep everything
⚠️ Be very careful with “Clear All”! This deletes trade history, not just log messages. Only use this when you want a complete fresh start.
When to Check the Activity Log
- After the market closes — Review what the bot did during the day
- When something seems off — Check for error messages or unexpected stops
- After a disconnect — See if the bot reconnected and what it did during the outage
- When the bot isn’t trading — Look for “no opportunities” messages or error events
💡 Tip: The Activity Log is your first stop for debugging. If the bot isn’t behaving as expected, the log usually explains why.