When troubleshooting trades not copying to follower accounts, start with one specific master order. Confirm the correct source account, the copier’s running state and the follower’s active configuration. Then compare the copy event with the follower’s broker order status. A filled master order does not prove that every follower filled.
Table of Contents
- Trades not copying to follower accounts: where to start
- 1. Confirm the copier workflow and source account
- 2. Check both broker connection and copier status
- 3. Review each follower’s account and active settings
- 4. Read pause, time-window and risk messages
- Error messages: what to inspect and what to change
- 5. Verify the expected quantity before blaming rounding
- 6. Check instrument mapping, contract and account permissions
- 7. Inspect order type, protection and exit behavior
- 8. Separate fill differences from missed copying
- 9. Check other copiers and current firm restrictions
- A worked example: one follower missed the entry
- What should you send PickMyTrade support?
- How to recover without creating duplicate exposure
- Retest the repaired route before resuming
- Frequently asked questions
Do not diagnose a copying problem from profit alone. Accounts can show different profit because of quantity, fill price, fees, previous trades or an exit that executed differently. To establish a missing or incorrect copy, compare the master and follower orders for the same event.
This PickMyTrade guide covers the ProjectX copier workflow on pickmytrade.io and the Tradovate Manual Trade Copier on pickmytrade.trade. It also explains how to separate those workflows from TradingView multi-account alert routing.
Quick check: Find the master order, locate the follower copy event, and inspect the broker order status. Compare requested quantity with filled quantity. Check exits and working protection before resending. Share the relevant master and follower order IDs privately with support; profit screenshots alone cannot establish the failed stage.
Trades not copying to follower accounts: where to start
Identify the mismatch before changing settings. No follower entry, a wrong quantity and a different realized profit are separate symptoms. Use the broker’s order record to establish whether an order was absent, rejected, working, partially filled or completed.
| What you see | First investigation |
|---|---|
| Every follower misses the entry | Source workflow, admin selection and copier running state |
| Only one follower misses it | Follower activation, account access and broker response |
| Follower has a working order | Order type, price conditions and broker session |
| Follower size differs | Submitted quantity, multiplier and filled quantity |
| Entry copied but exit did not | Exit event, remaining position and working protective orders |
| Positions match but profits differ | Entry/exit prices, quantities, fees and account history |
Preserve the event time and timezone. If you change accounts or restart the copier before recording the evidence, it can become harder to reconstruct which configuration was active when the order occurred.
1. Confirm the copier workflow and source account
Check where the source order originated and which feature should distribute it. The ProjectX guide documents manual orders submitted through PickMyTrade’s copier interface. The Tradovate manual workflow mirrors trades on its configured admin account. A multi-account TradingView alert route sends instructions to its configured destinations instead.
| Workflow | Documented source path | Reference |
|---|---|---|
| ProjectX copier | Trade Copier → Place Trade → Place Manual Order | pickmytrade.io |
| Tradovate manual copier | Selected Tradovate admin; manual trading through the supported source interface | pickmytrade.trade |
| Multi-account alert automation | TradingView alert with generated destination configuration | Broker-specific PickMyTrade alert setup |
For ProjectX, reproduce the issue using the path in the ProjectX Trade Copier guide. It covers ProjectX-to-ProjectX and ProjectX-to-Tradovate configurations. Do not assume an order entered in a different interface is covered merely because it trades the same account.
For Tradovate, check the admin selection against the Manual Trade Copier guide. It documents one admin account, active subaccounts and per-follower multipliers. A trade placed on another subaccount is not proof that the configured source route received it.
Avoid directing the same event to a follower through two routes unless the combination was deliberately designed and tested. An alert route plus another copier can create duplicate orders or exits.
2. Check both broker connection and copier status
A broker connection and a running copier are different states. Confirm the source and follower broker connections, then confirm the copier is started and connected. A saved follower list alone does not activate copying.
In the ProjectX setup, the documented sequence is to connect ProjectX, add the master and followers, and click Click to Start. If a connection drops, inspect the connection or copier message rather than repeatedly submitting orders while its state is uncertain.
Record any Disconnected, Connecting or Retrying state you observe, including its timestamp. After resolving the connection issue, use a fresh demo order to verify operation. Do not assume orders missed during an interruption are replayed automatically.
If an entry is already open when you restart, reconcile it first. Starting a copier is not sufficient evidence that pre-existing positions or working orders were synchronized.
3. Review each follower’s account and active settings
When only one follower fails, inspect that follower’s configuration independently. Verify the exact account ID, connection, environment and active setting. An account visible in a dropdown can still be unavailable for a new order.
Check whether the account changed after an evaluation reset, subscription change or move to another account stage. If the selected ID is obsolete, replace it through the supported setup flow and confirm the new connection. Reconcile existing positions before removing or replacing a route.
A follower under a different broker login may require additional connection and account-linking steps. Follow the guide for that broker. Do not assume that a token for one login authorizes all accounts under another login, or that one platform’s subscription rules apply to every integration.
4. Read pause, time-window and risk messages
A valid connection does not bypass configured trading restrictions. If the log reports a pause, time-window block or risk rejection, inspect that exact control and its scope. Resume or change it only when doing so matches your intended trading rules.
PickMyTrade’s error reference documents messages involving manual pause time, symbol blocks, missing mappings and account IDs not found in a connection. These messages are evidence about a specific processing path; they are not interchangeable diagnoses for every copier failure.
Compare the time window with the timestamp and offset in the error. Do not assume your computer’s local time matches the setting. US Eastern time also changes offset with daylight saving, so a label such as EST should not be treated as a fixed conversion throughout the year.
If the broker refuses an order for a position cap, margin or account restriction, changing the copier connection cannot override that rule. Check the follower’s current exposure and eligible order size.
Error messages: what to inspect and what to change
Use the exact error message to select the next check. The following messages are documented in PickMyTrade’s error reference. Some concern alert routing or ProjectX order configuration rather than the manual copier itself, so first establish which processing path produced the message.
| Message or error fragment | Inspect | Next action |
|---|---|---|
| Symbol Mapping Not Found | Submitted symbol and destination mapping | Map the intended broker instrument, then test the corrected route |
| Account id … not found in user connection | Configured account ID and current broker connection | Select the account actually present in the connection; regenerate the affected alert route when applicable |
| check manual trade pause time | Configured trading window and timestamp offset | Correct unintended time settings or wait for the permitted window; do not bypass an intentional restriction |
| Risk Settings – symbol is blocked | ProjectX Symbol Blocks and the intended risk policy | Change the block only if it is unintended and the account permits the instrument |
| Brackets cannot be used with Position Brackets. You must enable Auto OCO Brackets. | TopstepX bracket configuration for the affected route | Follow the current OCO setup guide and test protection before resuming |
A generic authentication or access error needs further investigation. Do not label an account breached or permanently unusable solely from the message. Check its provider status, authorization and current connection, then retain the full error for support.
5. Verify the expected quantity before blaming rounding
Compare three quantities: the master’s source order, the follower’s submitted order and the follower’s filled amount. A multiplier changes the intended destination size. A partial fill changes the amount executed so far. Those are different causes of a position difference.
| Master quantity | Follower multiplier | Illustrative expected instruction |
|---|---|---|
| 1 contract | 1 | 1 contract |
| 1 contract | 2 | 2 contracts |
| 3 contracts | 1 | 3 contracts |
| 2 contracts | 3 | 6 contracts |
If the master sends three contracts and each follower should receive three, use a multiplier of 1 for each destination. The number of accounts is not the multiplier. Check any other sizing rules that apply to the route before calculating the expected broker position.
Confirm the multiplier values accepted by your current setup before assuming how fractional sizing is handled. If a three-contract source becomes two contracts on a follower, inspect the submitted quantity, filled quantity and any rejected remainder. A rounding assumption alone does not establish the cause.
Use whole-number allocations for an initial demo test. Confirm the form’s permitted values and instrument quantity requirements before using fractional multipliers. Never increase size merely to force a failed order through.
6. Check instrument mapping, contract and account permissions
A follower must be able to trade the instrument the route submits. Compare the actual broker contract, not only the chart’s short symbol. Contract expiry, mappings, symbol permissions and account-specific product access can each prevent an otherwise valid copy.
If the log says Symbol Mapping Not Found, inspect the exact instrument configuration. If it reports an account-level block, investigate that restriction. A working mapping on the master does not prove that a different destination has permission to trade the same contract.
An Access is denied message can indicate an authorization or account-access issue; it does not conclusively prove that the account breached a prop-firm rule. Similarly, an entry ID error may involve a missing order relationship rather than a dead trading account. Preserve the complete message and inspect the associated account and event.
7. Inspect order type, protection and exit behavior
The source may fill while a follower order remains working or is rejected. Check the destination order type, requested price, time in force and submitted protection. Then confirm whether the copier supports the specific operation you expected it to replicate.
Tradovate’s manual-copier documentation lists unsupported advanced behaviors including trailing stops, automatic breakeven and multi-target setups. It also contains conflicting bracket instructions for non-market entries. Use the explicit market-entry bracket path for an initial test and confirm other combinations before relying on them.
If the entry copied but a stop or exit differs, inspect the working protective orders and fill records on every affected account. Do not assume stopping the copier flattens all positions or cancels every order. Establish the exact control’s scope from the current interface and verify the result.
For a partial exit, calculate the expected remaining quantity for each follower. A successful full-exit test does not establish partial-exit behavior. Test the operation you actually intend to use.
8. Separate fill differences from missed copying
Follower orders are processed independently. PickMyTrade’s Tradovate sync notice explains why fill timing and stop executions can differ in demo and funded environments. That does not mean every discrepancy is normal, or that an unmatched open position should be ignored.
Suppose two accounts both buy one contract and later sell one contract. If their entry or exit prices differ, their trade profit can differ even though both routes completed. Conversely, an account balance might appear close to the master’s while an unrelated working order remains. Order reconciliation identifies what actually happened.
Compare entry and exit executions, quantity, fees and the reporting period. Use balance screenshots to describe the concern, but use the associated orders to investigate it. A persistent position mismatch, missing protection or rejected order needs attention regardless of the displayed profit.
9. Check other copiers and current firm restrictions
Inspect any broker-native copier or second automation service targeting the same account. It may restrict direct orders or add another source of instructions. Identify which system should own the route before changing the configuration.
Topstep’s TopstepX documentation describes its own Trade Copier, which is a separate feature from PickMyTrade. Check the current account-stage restrictions and follower state there. Do not apply rules for the native copier to every external integration without checking the relevant policy.
A transition between evaluation, funded simulation and live accounts can change permitted access or features. Confirm the exact program’s current API, copier and trading rules with the firm. The setup working previously does not establish that the replacement account permits the same route.
A worked example: one follower missed the entry
This is an illustrative diagnostic example, not a reported customer test. The master buys two contracts. Follower A is configured at 1× and follower B at 2×. A has a two-contract position, while B appears empty. The expected instructions are two and four contracts respectively.
- Find the master entry order ID and filled quantity.
- Locate the corresponding copy event for follower B.
- If no event exists, inspect source routing, active settings and copier state at that time.
- If an event exists, read its message and locate B’s broker order ID.
- If the broker order is rejected, use the rejection reason; if working, inspect its price conditions; if partially filled, inspect the remainder.
- Reconcile the current positions before attempting any replacement order.
Do not send a second entry blindly. If the first order is working or delayed, resending can create excess exposure. Once the cause is resolved, reproduce the relevant case in demo and verify the exit as well as the entry.
What should you send PickMyTrade support?
Send evidence for one specific mismatch. Include the master order and the affected follower record so support can trace the event. Profit alone or a screenshot without identifiers generally cannot establish whether the order was submitted, rejected or filled differently.
| Evidence | Include |
|---|---|
| Source event | Master order ID, instrument, side, quantity, timestamp and timezone |
| Follower | Affected account reference and follower order ID if one exists |
| Processing | Exact copier/alert message and event time |
| Broker history | Master and follower order/execution exports for the same interval |
| Configuration | Copier state, source account, follower active setting and multiplier |
| Exit concern | Remaining position and working protective orders |
Compare exported master and follower histories over the same interval. PDFs or CSVs can help you identify the first unmatched event. Keep order IDs intact when sharing privately with support, because they are needed for investigation. Redact passwords, API keys, tokens and unrelated personal information.
How to recover without creating duplicate exposure
Recovery starts by establishing the current broker state. The missing-looking order may still be working, partially filled or delayed. Record that state, decide the intended position for each account and stop new entry signals through the control whose scope you have verified.
| Recovery step | Required check |
|---|---|
| 1. Preserve evidence | Save event times, order IDs, processing messages and current settings before changing the route |
| 2. Inspect every affected account | List filled positions, working entries, stops, targets and partially filled orders |
| 3. Define the intended outcome | Decide whether each account should remain in the trade or be flat; account for existing unrelated trades |
| 4. Resolve exposure at the broker | Use supported order/position controls for the intended account and quantity; verify any cancellation or close actually completed |
| 5. Handle working orders explicitly | Cancel only orders you intend to remove, then recheck whether a fill occurred during cancellation |
| 6. Repair one cause | Correct the account, connection, activation, size, instrument or time-window problem established by the evidence |
| 7. Restart and test | Use a fresh demo entry and exit from a known starting state before reactivating live entry signals |
Pausing new entries does not necessarily stop exits, flatten positions or cancel working orders. Likewise, stopping a copier can have connection-specific effects. Read its confirmation dialog and verify both master and followers after the action. Do not remove protective orders from an open position without a deliberate replacement or exit plan.
If your chosen recovery outcome is flat, verify zero intended exposure and no working orders that could reopen it on each affected account. A close request is not a fill confirmation. If an order state remains uncertain, contact support or the broker with its order ID before sending another entry.
Retest the repaired route before resuming
A fix is verified when a fresh demo entry and exit match the intended route. Record the starting positions and working orders, make one controlled change, then compare the actual results. Avoid introducing several configuration changes at once.
- Confirm the correct source and destination environments.
- Verify active connections, follower settings and expected quantities.
- Check time windows and broker restrictions.
- Submit one small supported demo order through the intended source path.
- Verify order status, filled quantity and protection on every follower.
- Test the exit and confirm remaining positions and working orders.
- Keep the successful records as a reference for the configuration.
For setup instructions, use the relevant official copier guide linked above. If the issue is multi-account alert routing, follow the Tradovate multi-account alert guide instead of treating an absent manual copy event as proof that alert delivery failed.
Frequently asked questions
Connected is only one check. Verify the source account and workflow, follower activation, account access, time-window or risk messages and broker order status. Use the log at the failed event’s time rather than only the copier’s current status.
Check that follower’s configuration and broker response independently. A wrong account ID, disabled route, access restriction, size rejection or working order can affect one destination while others execute. Trace the specific copy event before changing the group.
Not necessarily. Quantities, fill prices, exits, fees and earlier account activity can change profit. Compare the master and follower orders for the same event, including requested and filled quantity, before concluding that the copy was missing or wrong.
First check for working, delayed or partially filled orders and reconcile the current position. A blind resend can create duplicate exposure. Resolve the cause and test the corrected route in demo before resuming the intended workflow.
Share the master order ID for the mismatched event and the affected follower order ID if available. Include the timestamp, timezone, symbol and exact processing message. Send these privately to support and redact credentials rather than the order evidence needed to trace the issue.
When a follower mismatch is unresolved, stop new entries and reconcile exposure. Use PickMyTrade’s broker setup and support resources to verify the route, then complete a demo round trip before resuming live copying.
Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.
Also Checkout: Connect Tradovate with Trading view using PickMyTrade
