Prerequisites
- Copying stopped before changing safety-critical settings or restoring data.
- Broker positions and working orders checked before any restart.
- A secure destination with enough free space for backup export.
Appearance, notifications, and sounds
- Appearance offers System, Light, and Dark. System follows the operating-system theme preference where supported.
- Desktop notifications and sounds each offer Critical only, Warnings and critical, or Off.
- Native desktop notification delivery is currently implemented on macOS. The Windows setting does not currently produce a native desktop notification.
- Sounds work on Windows and macOS and are rate-limited to reduce alert storms.
- Alerts supplement Activity. Turning them off does not disable protection, risk rules, or issue recording.
Trading-day settings, history time zone, and Live P&L
Risk management uses a named time zone plus session close and next-session start. Dashboard, Trade log, and cloud records use the separate Trading time zone for midnight-to-midnight calendar dates. Changing either setting applies prospectively and does not rewrite all past records.
Enable Live P&L before relying on P&L-based rules. Enabling it does not buy market data or prove entitlement. Ready is normal while flat; test with a simulation position and look for Active.
Copilink Cloud sync
- Enable or disable cloud sync and choose the Trading time zone for history and web records.
- On first enable, Copilink can prepare older reconstructed history before ordinary uploading.
- Sync now retries eligible pending records while signed in.
- Offline records stay local and retry with increasing delay. Needs attention identifies an ownership, device, validation, version, or server-rejection condition that requires action.
- Disabling sync does not affect copying, protection, risk, connections, or the local Trade log. It prevents new web links from becoming ready.
| Cloud sync uploads | Cloud sync does not upload |
|---|---|
| Reconstructed trade-history and journal records needed for web review | Broker usernames or passwords |
| Eligible local sessions and journal data | Tradovate or Copilink session tokens |
| Identifiers needed to link a local session to its web view | A general raw broker-event dump, diagnostic logs, or support bundles |
Local data and storage
Data & storage shows the local trading-history location and database size. Open data folder asks the operating system to open its containing folder. Do not edit, move, or delete live data files while Copilink is running.
- Local data includes received order and fill activity, reconstructed sessions and journal data, known balance history, profiles, risk settings and state, preferences, and recent Activity history.
- Broker passwords, authorization sessions, and the Copilink desktop sign-in token are stored separately through secure operating-system facilities.
- The current product does not publish a reliable promise about which local items uninstall retains or removes. Export wanted data and follow current platform support guidance before uninstalling.
Export a backup
Stop copying when practical
Use a quiet period and confirm broker exposure before handling data.
Choose Export data backup
Select a secure destination with enough free space. The export is limited to approximately 2 GB.
Keep known-good copies
Store more than one copy on trusted storage and protect it as sensitive trading data.
A backup contains local trading history and credential-free configuration such as profiles, risk rules, and preferences. It excludes broker passwords, authorization sessions, and the Copilink sign-in token.
Copilink can also create an automatic local backup about once every 24 hours when no profile is active and retain up to 10. The current Settings page does not expose that schedule.
Restore a backup
Preserve the current state
Disable the profile, make broker exposure safe, and export the current data as a separate backup.
Select the exact backup
Choose Restore backup and select the intended file. Selecting a valid file stages the restore; the current UI does not show a second destructive confirmation.
Restart normally
Exit Copilink and start it again. Startup creates a pre-restore safety copy before replacement.
Reconnect deliberately
Reauthorize Tradovate and re-enter or re-add Rithmic access. Restored connections have Auto-reconnect off.
Review before enabling
Inspect profiles, ratios, symbols, risk rules, history, and actual broker exposure before enabling any profile.
What success looks like
- Settings show Saved after a change that must persist.
- Cloud state reaches Up to date when enabled and eligible records are linked.
- Backup export reports a validated snapshot at the intended secure location.
- A restore restarts into the intended data, with broker credentials re-entered and profiles reviewed before use.
Troubleshooting
- Settings will not save: stop relying on the visible change, check local storage and free space, and inspect Activity.
- Cloud delayed: confirm sign-in and internet, allow Preparing or Syncing to finish, then use Sync now after connectivity returns.
- Backup fails: check destination permission, free space, size, and file locks; try another trusted location.
- Restore fails: preserve current and safety copies, keep profiles off, record the exact message, and contact support before another attempt.
Still stuck? Open the full troubleshooting guide or email support@copilink.com.