Skip to content

14-day trial · Founding Rate live.

Browse the user guide

Stop-loss sync

With this option on, Copilink keeps the leader's stop-loss the same size as its open position, and each follower's copied stop follows at its ratio. It's off by default.

View Markdown

Before you start

  • A follower profile. Turn on Keep stop-loss quantity in sync in its editor, under Follower protection.

What it does

Say you're long 4 contracts with a 4-contract stop, and you take profit on 2. Without this option, the stop still covers 4 contracts, so if it triggers it would sell 4 and leave you short 2. With it on, Copilink resizes the stop to 2, and each follower's copied stop is resized at its ratio. It works the other way too: add to the position and the stop grows.

It also applies when you place a stop or change its quantity yourself. If the stop doesn't match your position, Copilink changes it back. Changing the stop's price is fine.

Where it works

If you trade with brackets or ATM strategies, leave this option off. Leave it off too if any follower's ratio is below 1.0, or if you deliberately keep a stop that covers only part of your position.

Each time you turn it on, Copilink asks you to confirm these requirements: every follower ratio at 1.0 or higher, one protective stop per instrument, and a stop you placed yourself as a standalone order. Press Enable SL sync to go ahead, or Keep off.

How it resizes a stop

  1. Something changes

    The leader fills part of an exit, adds to the position, places a stop, or has its stop quantity edited. Copilink waits a moment for the related updates to arrive.

  2. It compares

    It compares the leader's stop with the position your broker reports.

  3. It sends one change

    If they differ, Copilink asks the broker to resize the stop once and waits for confirmation. It never sends the same request twice.

  4. Followers follow

    When the broker confirms, each follower's copied stop is resized to the leader's new quantity × its ratio, rounded down. If that rounds to 0, the copied stop is cancelled, and Copilink places a new one when the size goes back above 0.

  5. Activity records it

    Stop-loss resized to the open position means it worked. Stop-loss left as placed means Copilink chose not to act and says why. If the broker rejects the change or doesn't answer, Activity says so, and you need to fix the stop at your broker.

If Tradovate says a stop can't be resized, Copilink stops resizing that order and shows one warning until the stop matches the position again. Your own edits to that stop are still copied. Other rejections, including every Rithmic rejection, are reported each time and tried again only after the position or the stop's price changes.

Stops it leaves alone

  • A stop on an instrument with no open position. Copilink can't tell a protective stop from a stop entry.
  • A stop on the same side as the position, such as a buy stop while you're long. That's an entry, not protection.
  • Two or more protective stops on the same instrument. How to split the size is your call.
  • A stop that has started filling.
  • A position your broker hasn't reported since the profile started.
  • Copied stops on followers that are off or disconnected.
  • Take-profit orders. Only stops are resized.

It manages only stops Copilink knows about: stops placed while the profile was running, and stops it picked up with their copies when the profile started.

Followers are sized from the leader

Check it worked

  • A partial exit on the leader shrinks the leader's stop and each follower's copied stop.
  • Activity shows Stop-loss resized to the open position.

If something goes wrong

  • A stop wasn't resized: open Activity. It says whether Copilink left the stop alone (and why) or the broker rejected the change.
  • The resize was rejected: fix the stop at your broker. With brackets and ATM orders this always happens, so turn the option off for that profile.
  • A stop you shrank on purpose grew back: that's the option working. Turn it off if you want partial stops.

Still stuck? Open Troubleshooting or email [email protected].