Most providers post updates after the entry. PipSync matches each one back to the position it belongs to.
| Message | What happens |
|---|---|
| "Move SL to entry" / "to BE" | Modifies the stop on the matched position |
| "TP1 hit, close half" | Partial close; the remainder keeps its stop and next target |
| "Move TP to X" | Modifies the target |
| "Close now" | Market close of the matched position |
| Anything unmatched | Logged, not applied. Never guessed onto another trade |
A modification the broker reports as "no change needed" counts as success — a stop already at the requested level is not an error.
Trailing stops
Off by default. When enabled per channel or account, the stop follows price at your configured distance and only ever moves in your favour.
- It runs server-side, so it keeps working when your machine is off.
- While trailing is active, a provider message that would move the stop backwards is ignored.
- Break-even and trailing combine: break-even first, then trail from a given profit distance.
When an update arrives too late
If the position already closed, the update is logged and discarded. That is why the log sometimes shows an unapplied "move to BE" right after a stop-out — the trade was already gone.