BTA / Delivery desk
Alert Cancellation vs Order Cancellation
An instruction withdrawal and a confirmed broker cancellation are different events.
A withdrawal belongs to the instruction history
A publisher can withdraw a call. That action should reference the original family and applicable version. Preserve the withdrawal message and its effective meaning, including whether it concerns a pending entry, a position instruction or another object. Removing the original from a feed does not reveal what happened in a recipient's account.
A recipient may have ignored, reviewed or acted on the earlier instruction. Do not assume all recipients share one state. A delivery record can show the observed withdrawal without establishing the account history. Keep an explicit no-order statement where known rather than manufacturing a broker acknowledgement for a message-only test.
A request may race another account event
A broker cancellation request is not necessarily a final response. An order can have partially filled or changed before confirmation. Retain quantities, identifiers and the responsible system's acknowledgement when actual account evidence exists. This is a logging distinction, not advice to cancel, resubmit or close a particular position.
The synthetic cancellation example in BTA's test kit concerns an instruction only. It supplies no broker state. An illustrative order race can teach why the distinction matters, but invented values must not become a named provider's observed execution history. A clear unknown state is preferable to an assumed flat account.
Define the review boundary
Ask the selected product who communicates withdrawal and who is authorised to modify exposure. Investigate whether retries or delayed originals are linked to the cancelled family. A newer receipt time should not automatically revive a withdrawn instruction. The destination's actual handling needs evidence, not an inference from the message wording.
Report instruction withdrawal received, account cancellation confirmed, or account status unobserved as separate findings. A page claiming all cancellations worked must identify which of those stages was tested and retain failed or missing responses. BTA has not conducted private account tests and will not award that claim from documentation alone.
Original Evidence Packet
| Artifact | Record to retain |
|---|---|
| Instruction | Original, withdrawal and effective authority |
| Account | Request, response, quantity and remaining state |
| Finding | Which cancellation boundary was actually observed |
Continue the Investigation
Source Boundaries
Official references describe published mechanisms. BTA's evidence packets and proposed test procedures do not claim a completed paid-feed or account trial.