Instead of executing one trade, C2 bought, then sold, then bought, then sold repeatedly, instead of executing as a single trade, burning PDT and not allowing proper executions of new trades due to PDT block.
This happened to me. I am now in PDT for a trade execution on C2s side. So now I’ll miss out on future trades for a week and risk account closure because of C2’s mistake.
this happened to me aswell, not only did it put my into PDT but I was left with incorrect positions for the strategy that I am following.
Agree — this should not have happened. The strategy is being driven by BrokerTransmit (we “read” events in the strategy manager’s brokerage account, interpret them, then replicate out to followers). We are trying to piece together exactly what happened in this specific case which caused the Buy and then Sell. We’ve reached out to the strategy manager to learn the specifics of the case from his point of view (order types, events, etc.) No imputation that the problem is on the manager’s side — it is 100% on C2’s side — but we don’t have an answer just yet.
I’m very sorry for this, and specifically that we caused the Pattern Day Trader on some accounts. We’re investigating this as a priority.
Update: I worked with c2 to hopefully resolve this going forward. Appreciate the prompt attention to this by the team.
Hey @MatthewKlein it happened again this morning tyy trying to execute on some trades. The orders placed and the final positions
Ok, two separate issues here.
- DarianGreenfield: We looked at the fills in your account (and your screen shot) and they actually matched the strategy perfectly. I wonder if the problem is that the activity looks quite “busy” - a fill, followed by another fill, followed by another, etc. In fact, this behavior is a new design (introduced just last week) that we implemented to make things better: previously we waited for the strategy to fill an order completely before sending orders out to follower accounts. This was a good choice 15 years ago when brokerage commissions were high and there was a “ticket charge” per order. But since that is no longer the case, last week we just made everything faster - we replicate partial fills as they happen. So now your executions will look like there is more activity going on, but in cases like this, it’s just individual pieces of a larger order being filled.
However…
- The second piece of this project was that we needed to make sure that Position Sync (the periodic check of the leader’s brokerage account versus the C2 Model Account) was aware of this new partial fill algo just introduced. Today we noticed Position Sync close a position that was partially filled. We fixed that. Going forward, Position Sync won’t “step on” partially filled/partially open orders.
