Tips & best practices

Use this page as a simple operating checklist. The goal is control and consistency: clear guardrails, predictable behavior, and quick troubleshooting when something looks wrong.

Daily routine (fast)

Before market (2 minutes)

  • Check readiness badges: fix anything showing warnings (especially access token).
  • Confirm budgets and limits on your active bots (capital, max loss, risk rules).
  • Start with Demo mode for any new bot or major change.

During market (light monitoring)

  • Watch Net P&L (Today) and open trades. Don’t chase every tick.
  • If results change suddenly, open the bot → Logs and Trades to understand why.
  • Use manual intervention only when your own predefined conditions are hit.

After market (10 minutes)

  • Review top losing bots/trades first (faster learning).
  • Note what you changed today (bot params, budgets, scripts) so you can correlate cause → effect.

General usage tips

  • Prefer stable routines over constant tuning: small, measured changes beat frequent tweaks.
  • Use Demo before Live: validate behavior in real market conditions without risking capital.
  • Review trade timelines when confused: the timeline + logs explain what the bot “saw” and did.
  • Set realistic budgets: keep lot size and capital aligned to your risk tolerance.

Working with bots

  • Keep access tokens valid: fix token warnings before you expect trades to execute.
  • Use filters instead of scrolling: status, P&L, date range, and bot type are the quickest path.
  • Use suggested scripts carefully: treat them as a starting point, then align with your risk plan.
  • Scale only what’s consistent: use win rate, trade count, and P&L trend—not a single good day.

Working with trades

  • Use Today vs Overall: separate short-term noise from long-term performance.
  • Inspect losing trades first: charts + logs help you spot repeated mistakes (timing, sizing, rules).
  • Filter aggressively: bot, instrument, CE/PE, status, and P&L filters save time.

Operational hygiene

  • Check process logs occasionally: long runtimes or errors usually explain missing updates/trades.
  • Keep auto-refresh sensible: faster refresh doesn’t improve execution quality.
  • Write down your configuration: so you can reproduce what worked (and roll back what didn’t).