Getting Started

Use the first week to prove reliability before you scale

The goal of week one is not speed. It is confidence. This checklist updates the old Freshdesk advice for the current DaneTrades model, including the local runtime, Copy Health, Logs, current billing flow, and modern platform coverage.

  • Focuses on reliability before live size
  • Built for the current local-runtime setup
  • Applies to both direct account copying and supported signal sources

Quick answer

During the first week, optimize for proof and stability, not volume:

  • Test on demo or the smallest sensible size first.
  • Keep the local runtime online and stable.
  • Check Logs and Copy Health after every meaningful test.
  • Confirm symbol mapping before assuming a platform issue.
  • Scale slowly only after repeated clean results.

Checklist for the first week

  1. Confirm your workspace and billing are in order. Make sure your trial or plan is active, you can access the web app, and the local runtime is connected from Download Agent.
  2. Keep the first tests small. Use demo or the minimum practical live size while you validate connections, sizing, and symbol behavior.
  3. Test more than one symbol. Run several small trades, especially on symbols that commonly vary across brokers such as gold, indices, or crypto pairs.
  4. Review symbol mapping deliberately. If source and receiver symbol names differ, set mapping before you treat the setup as reliable.
  5. Watch Logs and Copy Health after every test set. Do not rely on account history alone. The logs explain rejections, skipped actions, and any mismatch that needs attention.
  6. Scale live in stages. Increase size only after several clean sessions, not after one successful trade.

Operational checks that matter most

  • The PC or Windows VPS stays awake, connected, and signed in.
  • The source and receiver accounts remain connected in the app.
  • Sizing rules are conservative and make sense for the receiver balance.
  • Stop-loss dependent risk logic is only used when your source provides that data consistently.
  • No repeated invalid volume, insufficient margin, or symbol errors appear in Logs.

When to stop and fix the setup first

Pause and investigate before scaling if any of these show up:

  • Trades copy on some symbols but fail on others.
  • The runtime drops offline or disconnects under normal use.
  • The receiver size is inconsistent with your intended rules.
  • Logs show recurring broker rejections or mapping issues.
Best next move: go back to the quickstart guide, retest with a tiny trade, and use the support portal only after you have the latest log details ready.