5. Manage messages and operating controls
A setup contains separate broker actions. One leg can fill while another fails. Inspect the journal and broker records rather than forcing a resend.
Know what each control does
These controls do not automatically close positions or cancel pending orders. Closing the browser alone does not stop the host. Restart begins Paused and does not replay old entries. Do not force-close a host with an unknown broker result.
| Control | Effect |
|---|---|
| Start | Allows eligible new entries after all guards pass. |
| Pause | Blocks new entries; authorized protection may continue while connected. |
| Emergency / Reset | Latches the entry block. Reset returns to Paused, not Start. |
| Disconnect | Waits for an in-flight action, then stops software management. |
Interpretation, replies and original edits
- Clear fresh messages still need every source/account/license/schedule/risk check. Waiting, invalidation, conflicting negation and unsupported conditions require review. A correction of direction or shortened prices needs one uniquely supported interpretation.
- Original-message edits do not automatically rewrite existing orders. A management instruction must link clearly to the owned setup; an unresolved reply must not guess the latest trade.
- Partial close requires an explicit fraction and valid volume rounding. Unsupported future conditions are not immediate closes. Source target changes may place target-based protection on Hold; inspect Operating status.
- Images/OCR and browser ambiguity approvals do not execute trades. Browser manual tools remain preview-only, and existing manually opened MT5 positions are not automatically adopted.