Skip to main content

Why did replication fail during a futures contract rollover?

Replication failures during rollover periods are caused by a timing mismatch between brokers — one platform has rolled to the new front-month contract while another has not.

If replication has stopped working and it is around the time futures contracts roll to a new expiry month, a contract mismatch between your leader and follower platforms is the most likely cause. One broker has already switched to the new front-month contract while another is still on the expiring one — and Tradecopia is sending orders for a contract the follower's broker is not expecting.

You might be experiencing this if:

  • Replication stopped working around contract rollover time

  • Follower orders are being rejected near the end of the month

  • Your accounts show different contract months for the same instrument

  • Replication worked fine yesterday but broke overnight near month-end

Why this happens

Futures contracts expire on a regular schedule and brokers switch to the new front-month at slightly different times. Tradecopia replicates orders on the contract the leader is currently trading. If the follower's broker is still on the old contract — or has already rolled while the leader has not — the replicated order arrives for the wrong contract cycle and the broker rejects it, misroutes it, or ignores it.

This is a timing mismatch between broker platforms, not a Tradecopia failure. Once all platforms are on the same contract, replication resumes normally.

This issue most commonly affects users running different brokers across leader and follower accounts. If your leader and all your followers use the same broker, that broker typically rolls all accounts at the same time, so timing mismatches are rare. The risk is highest with mixed setups — for example, a Rithmic leader with Tradovate or TopStepX followers.

Rollover windows to watch

If replication fails and the date falls within one of these windows, contract mismatch is the first thing to check.

Contract

Rolls in

Approximate window

ES, NQ, RTY, YM

March, June, September, December

Around the 2nd week of the expiry month

CL (Crude Oil)

Monthly

Around the 3rd week of the prior month

GC (Gold)

February, April, June, August, October, December

Around the last week of the prior month

These are approximate windows — exact rollover dates shift slightly each year. Check the CME Group website for precise expiry and first notice dates if needed.

How to fix this

1. Check which contract each platform is trading

Open your leader platform and each follower platform and confirm they are all showing the same active front-month contract. Look at the contract symbol — for example, ESM5 is a different contract from ESH5. If any platform is showing a different month, that is the mismatch.

2. Roll the platform that is behind

If one platform is still on the expiring contract, switch it to the new front-month. Most broker platforms and trading frontends have a dedicated rollover tool or prompt for this. If you are unsure how to roll on a specific platform, check that broker's support documentation.

3. Confirm all platforms are synchronised

Once rolled, verify the leader and all follower platforms are showing the same active contract symbol before resuming any trading.

4. Flatten before resuming

Use Group Flatten in Tradecopia to clear any residual positions or orphaned orders that may have accumulated during the mismatch period. Do not resume copy trading until the group is clean.

If any residual positions remain after Group Flatten and cannot be closed through Tradecopia, close them manually on the broker platform directly — the contract may no longer be tradeable through Tradecopia if it has already expired.

Related articles

Did this answer your question?