Forex expiry, requotes and order-state review
Keep active, unfilled, expired, rejected and amended instructions distinct through a forex order lifecycle.
An instruction can exist without exposure
An original signal can name an entry condition while no position has yet been filled. Preserve its validity interval, activation condition and the intended order type. A working order, an acknowledged request and a filled position are different states. The review should not assign exposure solely because a message was published.
Read the exact product and account documentation for the intended route. MetaTrader trading principles provide a platform reference for orders, deals and positions. They do not establish that every signal service uses the same expiry or handling rule. Save the instruction version that controlled the consumer's decision instead of borrowing a later favourable interpretation.
A rejection is a workflow event
Keep a rejection, cancellation or returned price response in the record with its time and reason when available. It may explain why a subscriber path differs from a source path. Do not automatically classify an unfilled instruction as a winner or loser because the later market move would have produced that outcome.
An account request can also be partially executed before another part expires or is cancelled. The remaining order state and held quantity must then be reviewed separately. The new journal begins from supplied executed or expressly hypothetical lots; it cannot infer these order states from a price chart or turn an acknowledgement into a complete fill.
Amendments need a parent and an effective boundary
Identify whether a later message changes an unfilled original, changes an existing position or introduces a new idea. Its publication and subscriber availability are separate clocks. An earlier unchanged record should not silently become evidence that a later level was available at the earlier decision time.
Preserve any uncertainty in timestamp precision. Two records displayed in the same second do not necessarily reveal the order within that second. The teaching chronology accepts supplied labels for consistency checks, not authentication. A real causal assessment needs the relevant source records, applicable route and the declared rule for which version owned each action.
Compare a cutoff without inventing a fill
Choose a fixed observation cutoff and list active, expired, rejected, cancelled, fully closed and open states under a stated population convention. A journal mark values entered remaining lots; it is not an executed final close. An unfilled original has no entered economic lot to mark.
The distinction prevents a tidy spreadsheet from acquiring fictional executions. Keep both instruction and position inventories when reviewing a service. The two inventories can be linked without having identical counts. A delayed-entry sensitivity exercise and a lifecycle record answer different questions, and neither replaces a source-linked account execution history.
Use an exception log rather than a forced verdict
For each unresolved event, record the original ID, intended action, exact state, missing relationship and the document that would settle the question. A clear exception can guide a compatibility decision more effectively than a broad allegation. Some workflows may supply the answer in a platform export or account specification rather than a promotional page.
The new packet includes deliberately rejected numerical cases so readers can see what the arithmetic refuses to assume. Those cases are not reports of actual provider errors. Retaining the error and its input keeps the educational result honest while supporting more precise review questions.
Reference documents
These references cover mechanisms and source definitions. The worked numbers on this page are invented teaching inputs, not provider or account records.