FAQ
Check on-screen error messages first, then cross-reference with the scenarios below. This page does not supersede live task details or actual exchange order states.
The questions below are organized across four lifecycle phases: Binding → Admission → Execution → Reconciliation. Each entry details what to check first, common root causes, and what to avoid doing.
What to Do When API Binding Fails
Check exchange selection, verify Key and Secret match, and confirm OKX Passphrase is correct. Verify Read and Futures Trading permissions are enabled, Withdrawal and Transfer are disabled, and the IP whitelist contains only the platform egress IP shown on the form. See Permissions.
Correct permission errors before retrying. When submitting feedback, provide the error message and timestamp; never transmit full credentials.
Error Message Cross-Reference
| Error Message (Meaning) | True Cause | How to Fix |
|---|---|---|
| Key failed exchange permission check | Exchange rejected read-only probe | Verify key is active, unexpired, and Key/Secret match |
| Key has withdrawal permissions enabled | "Enable Withdrawals" is ON | Disable withdrawals on exchange (some venues require recreation) |
| Key has universal transfer enabled | Funds can be moved across wallets | Disable universal transfers |
| Key has internal transfer enabled | Same as above | Disable internal transfers |
| Key has no IP whitelist bound | Whitelist is empty | Paste the platform egress IP into the exchange whitelist |
| Key lacks futures trading permission | Futures box unchecked | Enable futures trading permissions |
| Key lacks read permission | Reading box unchecked | Enable read permissions |
| Account is not in Hedge Mode | Exchange is in one-way mode | Switch futures position mode to Hedge Mode (dual-side) |
| Check label, API Key, Secret, and Passphrase format | Field empty, too short, or invalid chars | Key must be ≥ 8 chars, Secret required, OKX requires Passphrase |
| Reached quota of N keys | Maximum bound keys reached | Unbind unused keys first |
| Service is currently paper-only | Host deployment disabled live | No action required; paper copy is fully functional |
Diagnostic Order
- Verify Key and Secret belong to the same pair. Pasting mismatched pairs is the most frequent mistake.
- Review the permission triad. Read enabled, Futures enabled, Withdrawal and Transfer disabled.
- Verify IP settings. Blank whitelists, multiple IPs, or outdated IPs will fail.
- Check position mode. One-way mode is frequently overlooked.
- Inspect account standing. Expired keys, exchange risk blocks, or sub-account limits.
What NOT to do: Rapidly retrying with identical unedited configurations; pasting Key and Secret into support chats "for engineers to check"; taking unredacted screenshots.
TODO 素材：此处补「API 权限校验失败提示及对应检查项，不包含凭据」截图
Why Live Copy Is Unavailable
Confirm you are signed in, your account holds live copy authorization, and a verified, compliant API Key is selected. Check if available capital loaded successfully, ensure plan or authorization quota is sufficient, and confirm pre-flight returned no blocking errors.
If capital numbers are temporarily unavailable, use the on-screen "Re-read" button; do not treat outdated balances as active quota. See Capital & Positions.
Common Ineligibility Reasons
| On-screen Prompt | Meaning | What You Can Do |
|---|---|---|
| No live invite or invite revoked | Live copy is invite-only in beta | Contact support@copysonar.com to apply |
| Live authorization expired | Authorization has a validity window | Contact administrator to renew |
| Current plan does not support live | Plan tier is paper-only | Upgrade plan or continue with paper mode |
| Exceeds authorized live capital limit | Capital exceeds authorized cap | Reduce allocated capital |
| Live copy slots currently full | Egress IP capacity reached | Try again later |
| Site has not enabled live copy | Deployment policy disabled live | Wait for site-wide enablement |
| Account risk budget not configured | Missing risk budget parameters | Contact administrator to set up |
| Stopped new risk; reductions allowed | Risk controls intervened | Check specific reason; admin review usually required |
| Key verification expired | Last verification > 24 hours ago | Go to API Keys and click "Check Permissions" |
| Key already has live copy running | One key can only run one live task | Switch keys or stop the existing task |
| Existing positions detected | Non-task positions found in account | Handle on exchange before launching |
| Margin mode mismatch | Margin mode conflicts with settings | Adjust settings on exchange |
Four-Step Self-Check
- Login & Plan: Ensure you are signed in and plan quota is not exhausted.
- Key State: List must indicate "Permissions Valid", not "Blocked".
- Capital Reading: Page displays a numeric value, not
—. - Pre-flight: If pre-flight flags blocking errors, fix them rather than repeatedly clicking launch.
What to Do When Running but No Trades Occur
Confirm the task's mode (Paper / Live) and active state, then check for new actionable signals. Entry rules, symbol whitelists, direction filters, slippage caps, and chase windows all affect whether an order is placed; do not widen risk parameters simply because no trades have occurred yet.
Inspect execution receipts in task details, and verify orders and positions directly on the exchange. Paused status does not mean positions are closed, nor does a drawdown trigger mean positions are liquidated. See Entry & Risk Controls.
Inspect Missed Trade Logs First
Task details' "Execution Receipts" list every dropped signal and its exact cause; this is the quickest diagnostic tool:
| Missed Reason | Explanation | Usual Fix |
|---|---|---|
| Chase timeout (exceeded chase window) | Signal arrived late or window was too short | Moderately extend chase window, or accept skip |
| Slippage exceeded (exceeded max slippage) | Market price moved past slippage cap | Relax slippage cap, or follow higher-liquidity coins |
| Precision below exchange minimum order size | Position too small to meet lot size | Increase capital or single-coin cap |
| Insufficient available margin | Account available balance too low | Lower leverage/position, or top up balance |
| Exchange API rejected order | Exchange rejected (parameters, risk, rate limit) | Review exchange error response; rotate key if needed |
| Network disconnected or excessive latency | Execution environment anomaly | Observe if persistent; contact support if ongoing |
| Triggered symbol whitelist/blacklist filter | Coin not included in whitelist | Check if whitelist is overly restrictive |
| Triggered direction filter (long/short only) | Signal direction conflicts with setting | Confirm direction matches your strategy |
| Triggered 24h volume ranking filter | Coin volume rank outside range | Adjust volume ranking threshold |
| Lead trader capital below minimum threshold | Trader equity is too low | Select another trader |
| Margin mode conflicts with existing position | Coin already held in conflicting mode | Standardize margin mode on exchange |
If the Missed Trade Log Is Empty
This indicates no actionable signals were generated, not that execution failed. Verify:
- Is task status "Running"? "Paused", "Reduce Only", or "Terminating" tasks do not open new trades.
- Has the lead trader traded recently? Check trader reports for latest activity timestamps.
- Does your whitelist accidentally exclude the trader's primary trading pairs?
- Was the task just created? When "Follow new orders only" is selected, historical positions are not copied.
What NOT to Do
- Crank slippage caps to extreme levels because "nothing filled".
- Expand chase windows to hundreds of minutes because "nothing filled".
- Jack up capital or risk multipliers out of impatience.
Zero fills typically mean protective mechanisms are doing their job. Understand the underlying reason before adjusting any setting.
TODO 素材：此处补「任务状态、执行反馈与当前持仓的查看位置」截图
Why Simulation, Task PnL, and Balances Differ
Paper simulation routes no real orders; execution prices, latency, and fees inevitably differ from live trading. Configured capital, effective capital, occupied margin, and exchange balance are distinct indicators.
Review units, time ranges, and fee accounting for each metric; unrealized PnL shifts with market prices, and funding fees may be recorded separately. When data is loading or missing, wait for recovery or cross-check exchange records; never treat missing numbers as zero.
Six Commonly Confused Numbers
| Metric | Definition | Common Misunderstanding |
|---|---|---|
| Allocated Capital | Copy capacity allocated to the task | Treating as locked margin |
| Effective Capital | Active baseline for position sizing (may fall below configured) | Overlooking that it has dropped |
| Task Equity | Effective capital + Realized PnL + Unrealized PnL | Treating as total exchange balance |
| Realized PnL | Profit/loss from closed positions | Forgetting funding fees may be excluded |
| Unrealized PnL | Floating profit/loss of open positions | Treating as finalized cash in hand |
| Funding Fees | Perpetual swap funding cashflows | Assuming it is already inside trade PnL |
Why Simulation and Live Diverge
| Difference Source | Paper Copy | Live Copy |
|---|---|---|
| Fill Price | Reference price fill | Real book execution with market impact |
| Latency | Zero | Network + matching + queuing (usually hundreds of ms) |
| Trading Fees | Often omitted | Deducted according to exchange fee tiers |
| Funding Fees | Often omitted | Incurred based on holding duration and rates |
| Partial Fills | Usually 100% filled | Partial fills or drops can occur |
It is normal for paper returns to be 30% while live returns are 10%; the inverse can also happen depending on market regime.
What to Check When Numbers Do Not Add Up
- Confirm Scope: Clarify whether you are looking at task-level or account-level metrics. Task equity does not equal overall exchange balance.
- Check Timestamps: Page data represents a snapshot time; exchange data is live. Time skews naturally exist.
- Verify Effective Capital: Reduced capital simultaneously shrinks position sizing and recalculates drawdown baselines.
- Inspect Fees: Check whether funding and maker/taker fees are itemized separately.
- Notice Missing Values:
—signifies data yet to return, not 0.
If figures still diverge, contact support@copysonar.com with Task ID, timestamp, and exchange statements. Do not attach API credentials.
What Task Statuses Mean
| Status | Meaning | Opens New Positions? | Closes Positions? |
|---|---|---|---|
| Pending Start | Created; engine has not yet taken over | No | No |
| Running | Normal signal following | Yes | Yes (follows trader) |
| Paused / Paused · Reduce Only | Halts new risk | No | Yes (reduce only) |
| Reduce Only | Risk stop or budget triggered | No | Yes |
| Terminating / Liquidating | Ending task and handling positions | No | Yes (per chosen method) |
| Funding Settlement | Position closed; awaiting funding settlement | No | No |
| Liquidation Complete | Positions closed; task wrapping up | No | No |
| Launch Rejected | Engine rejected start; see reason | No | No |
| Stopped / Archived | Task concluded; automatic management ended | No | No |
"Launch Rejected" is not a system outage; it indicates parameter or admission requirements were not met. Correct the issue and recreate the task.
Contacting Support
- Email: support@copysonar.com
- Provide: time of incident (with timezone), on-screen error text, Task ID, redacted screenshots.
- Never provide: API Key, Secret, Passphrase, account passwords, 2FA codes.
If you suspect credential compromise, delete the Key on the exchange first, then contact us. Order of operations matters: revoking access always takes precedence over root cause analysis.