Reference / Trade execution

Changing work already sent

The route a change takes from the caller to the venue, and the arm it leaves by for each way of working. Each sentence hands off to the article owning the behaviour it names, and the order they happen in is proved below rather than borrowed.

Contents

Starts from a caller asking Praxis to alter work it has already submitted.

Ends with the work altered, with the change refused on the call, with it logged and returned where the caller hears nothing, or with it set aside for a later pass.

Before the worker sees it

  1. The settings a change carries are built before any of this, and must name the command, the account and a reason — one with nothing set at all cannot be made — The change each way of working accepts.

  2. The host refuses a change while it is shutting down, before it has been started, and while the named account is not ready — What the host refuses first.

  3. The checks that turn a change away happen here, before it is queued, not on the worker: a command already ended with no protection of its own left to amend is answered as a no-op — The change each way of working accepts. A change to a single order naming either of its stop prices is refused, whichever side it is — The change each way of working accepts. So is one asking to alter a weighted run's weights — The change each way of working accepts. So is one raising what a buy commits, the caller told to place a new order instead — The change each way of working accepts.

  4. Everything admitted joins the priority line — every kind, with none going to the venue from here — Changing work already sent.

  5. The worker's next pass takes that line — How waiting work is drained.

  6. A change reaching it while the account is catching up with the venue is put back rather than carried out, and tried again on a later pass — A change waiting out a hold. A poisoned account holds it the same way, and that hold does not lift while the host runs — When an account is reconciling or poisoned.

One arm per way of working

  1. Arm one — a protective pair. A change naming one is dispatched before any other check here — Changing work already sent — and takes its own route from there — How protection's prices are changed.

  2. Past that arm a command that ended while it waited is answered as a no-op, this being the second such check and the one that catches it — Changing work already sent.

  3. A command the record has no entry for takes nothing, and so does one whose previous change is still settling, which keeps two from being in flight at once — Changing work already sent.

  4. Arm two — work fed out over time. The count of parts and the gap are altered, and only a new count plans the remaining amounts again — How a schedule change is carried out.

  5. Arm three — a ladder. The whole grid is replaced: the old rungs come down and are confirmed over before any new rung goes up — How a ladder's prices are changed. What can leave that grid short is its own matter — What stops a ladder's new rungs.

  6. Arm four — a single order or a part-shown one. A change whose settings match neither kind is refused here, a second time: the first such refusal was the raise before it was ever queued — The change each way of working accepts.

  7. An order the record has as anything but resting at a named price is refused — Changing work already sent. A part-shown order's change may name the amount to show, the price, or both, and whichever it leaves out keeps the value it had — What each change insists on.

  8. Otherwise the order is replaced: cancelled, settled, and a fresh one placed for what is left — How a price change is carried out. Where the figures cannot be settled, the change is parked and the original left unfinished — How a price change is carried out. Where the cancel itself is unconfirmed, nothing is placed and the order is left live — When a price change places nothing.

Where this route is not taken


Created 2026-10-15 08:20 UTC · Last modified 2026-10-23 07:08 UTC

Source evidence
---
row: S-03
baseline: 49aa659
created: 2026-10-15 08:20 UTC
modified: 2026-10-23 07:08 UTC
evidence:
  - claim: "The host's own refusals run before the manager is reached"
    source: "`trading.py` 1913-1916 before 1917, handed on at `trading_inbound.py` 262 into `execution_manager.py` 3048"
  - claim: "Every admitted change is queued, none going to the venue from here"
    source: "`execution_manager.py` 3060-3072 into 3074"
  - claim: "A protective pair's change is the first arm inside the pass, before the ended-command check"
    source: "`execution_manager.py` 8616-8620 before 8622-8624"
  - claim: "An unknown command and an unsettled previous change are refused past that arm"
    source: "`execution_manager.py` 8627-8629 and 8631-8636"
  - claim: "A run and a ladder take their own arms, and return from them"
    source: "`execution_manager.py` 8639-8646 into 8653"
  - claim: "What is left is a single order or a part-shown one, anything else refused"
    source: "`execution_manager.py` 8655-8661"
  - claim: "The stop-price, weighted-field and buy-exposure refusals all run before the change is queued"
    source: "`validate_trade_modify.py` 200-208, 210-218 and 220-226, reached from `execution_manager.py` 3060 before 3074"
  - claim: "A command ended with protection of its own left to amend is carried past the ended-command check"
    source: "`validate_trade_modify.py` 171-175"
  - claim: "An order the record has as anything but resting at a price is refused on the worker"
    source: "`execution_manager.py` 8680-8684"
  - claim: "A part-shown order's change takes the named price or the one the order had, and the named amount or the one it had"
    source: "`execution_manager.py` 10215-10225"
  - claim: "The settings must match the way of working before the change is queued, and are matched again on the worker"
    source: "`validate_trade_modify.py` 193-198 before `execution_manager.py` 8655-8661"
---

Edit this sourceCheckout revision · 7381aa49
Reference / keep your place
Find a passage