# C2 Autosync No longer Working? **URL:** \ **Category:** C2\ **Created:** [August 13, 2026, 2:16pm UTC](https://forums.collective2.com/t/c2-autosync-no-longer-working/17111 "2026-08-13T14:16:00Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![GaryLynn2](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/garylynn2/32/23549_2.png) [@GaryLynn2](https://forums.collective2.com/u/GaryLynn2)\ **Post date:** [August 13, 2026, 2:16pm UTC](https://forums.collective2.com/t/c2-autosync-no-longer-working/17111/1 "2026-08-13T14:16:00Z")
I autotrade the ares system and soon after the open this morning the system went long MNQ. The stop order was rejected because the price had already moved beyond the stop. This is an issue with Tradovate and is not C2’s fault. However, Autosync was on and it should have gotten me into the long position a couple of minutes later. It has been over 30 minutes and my account is still flat. ---
**Author:** ![DanW](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/danw/32/238_2.png) [@DanW](https://forums.collective2.com/u/DanW)\ **Post date:** [August 13, 2026, 2:25pm UTC](https://forums.collective2.com/t/c2-autosync-no-longer-working/17111/2 "2026-08-13T14:25:47Z")
The same exact thing happened to me: The trade was missed due to it pushing past the stop entry too fast, but Autosync did not kick in, so I completely missed this trade. The Collective2 backtesting results are not accurate if trades don’t happen in real trading. ---
**Author:** ![test123456](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/test123456/32/23804_2.png) [@test123456](https://forums.collective2.com/u/test123456)\ **Post date:** [August 13, 2026, 3:26pm UTC](https://forums.collective2.com/t/c2-autosync-no-longer-working/17111/3 "2026-08-13T15:26:13Z")
This also happened to me ---
**Author:** ![BertGreene](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/bertgreene/32/21057_2.png) [@BertGreene](https://forums.collective2.com/u/BertGreene)\ **Post date:** [August 13, 2026, 3:33pm UTC](https://forums.collective2.com/t/c2-autosync-no-longer-working/17111/4 "2026-08-13T15:33:26Z")
Same thing happened to me! ---
**Author:** ![FrancisGingras](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/francisgingras/32/23692_2.png) [@FrancisGingras](https://forums.collective2.com/u/FrancisGingras)\ **Post date:** [August 13, 2026, 3:45pm UTC](https://forums.collective2.com/t/c2-autosync-no-longer-working/17111/5 "2026-08-13T15:45:35Z")
Hi guys, The strategy sent a stop order so close to the market that by the time it got to brokers, the market had already moved past the order price and all brokers rejected it. But why did C2 not resync your account a few minutes later? Back in June 2026, we made changes to AutoSync: we mostly stopped synching to open new positions. Instead of continuously trying to open missing positions in your account, we now Sync to open new positions only when you set up a new strategy, or when you change your AutoTrade settings. You can also tell us to try again to open new positions at any time by clicking the new “ReSync” button that will soon appear on your AutoTrade Control Panel. This change only affects the way we _ **open** _ new positions: AutoSync will continue to monitor your account and **close** any positions that should be closed, or reduce trade sizes as needed, just as it always has. Nothing will change there. Probably, most of you have not noticed the change, but remember: if you ever find yourself in a situation where our first attempt to open a trade is rejected by your broker (for example: insufficient margin in your account, or like in this case where a strategy signal was rejected by brokers), then you can always press the ReSync button to force a full re-sync (including open positions). I hope this helps. ---
**Author:** ![MatthewKlein](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/matthewklein/32/21382_2.png) [@MatthewKlein](https://forums.collective2.com/u/MatthewKlein)\ **Post date:** [August 13, 2026, 3:52pm UTC](https://forums.collective2.com/t/c2-autosync-no-longer-working/17111/6 "2026-08-13T15:52:54Z")
Also I think this was posted as a “what’s new” alert back when implemented: > **[What is ReSync?](https://support.collective2.com/hc/en-us/articles/360008908033-What-is-ReSync)** > > Introducing the new AutoSync > If you've been AutoTrading for a while, you know about AutoSync. It's the way Collective2 ensures your brokerage account stays in sync with the "intentions" of the stra... ---
**Author:** ![GaryLynn2](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/garylynn2/32/23549_2.png) [@GaryLynn2](https://forums.collective2.com/u/GaryLynn2)\ **Post date:** [August 13, 2026, 4:02pm UTC](https://forums.collective2.com/t/c2-autosync-no-longer-working/17111/7 "2026-08-13T16:02:00Z")
I guess you had your reasons for making this change. Now that I know that C2 will not make the trade for me in this scenario (which has happened several times with Tradovate) I’ll perform the sync myself. I know that most people are not in front of their screens all day watching the trades as I do, so they will just end up missing the trades…which will likely be profitable like today. ---
**Author:** ![GaryLynn2](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/garylynn2/32/23549_2.png) [@GaryLynn2](https://forums.collective2.com/u/GaryLynn2)\ **Post date:** [August 13, 2026, 4:10pm UTC](https://forums.collective2.com/t/c2-autosync-no-longer-working/17111/8 "2026-08-13T16:10:26Z")
I just performed the resync. Is it supposed to issue the profit limit and stop loss orders, or do I need to rely on the autosync to get me out if the stop is hit? ---
**Author:** ![GaryLynn2](https://yyz2.discourse-cdn.com/flex028/user_avatar/forums.collective2.com/garylynn2/32/23549_2.png) [@GaryLynn2](https://forums.collective2.com/u/GaryLynn2)\ **Post date:** [August 13, 2026, 4:12pm UTC](https://forums.collective2.com/t/c2-autosync-no-longer-working/17111/9 "2026-08-13T16:12:55Z")
It took several minutes, but the orders did appear.