Account safety notices: broker verification required
Account safety notices are a banner that appears when the application cannot prove what happened to a linked stop and target pair at the broker. Each notice names the account and connection and asks for a human check before it clears.
Senzoukria · Documentation · Updated September 2026
Where to find it
- Where
- In the application shell, above the current screen
- Heading
- OCO — broker verification required (<count>)
- Source
- Linked stop and target (OCO) handling only
- Severity
- verification-required
- Expiry
- None. No timeout, no automatic resolution, no retry
- Scope
- This window's memory only; nothing is written to disk
What it does
The banner is an alert region listing one entry per unresolved notice. Each entry prints the account number and the connection identifier on one line, the exchange and instrument on the next — or "Instrument not supplied" when the broker did not name one — then the message itself, then a button reading "I checked positions and orders for <account>".
It is mounted in the application shell rather than inside a screen, so changing account or navigating elsewhere cannot hide a pending uncertainty. A closing line states plainly that your acknowledgement clears only the notice you acted on.
The store behind it is deliberately independent of the account feed and of transient order notes. It survives navigation and disconnection, it never expires, it never resolves itself, it never asks the broker anything and it never retries. Only a human acknowledgement removes an entry, and a later emission may warn again about the same account.
What a notice contains
| Setting | Default | What it changes |
|---|---|---|
| Account | always present | The broker account the uncertainty concerns |
| Connection | always present | Which saved connection produced it |
| Instrument | may be absent | Shows exchange and symbol, or "Instrument not supplied" |
| Message | always present | The raw explanation of what could not be confirmed |
| Acknowledgement button | one per notice | Removes that notice only; it sends nothing to the broker |
| Duplicate handling | ignored | A notice with an identifier already listed is not added twice |
How to use it
- Open your broker's own platform and inspect positions and working orders for the named account.
- Cancel or flatten there if anything remains that you did not intend.
- Only then press the acknowledgement button. Pressing it is a statement that you checked, not a request to the broker.
- Treat a notice that reappears as a new uncertainty about a new event, not as the old one coming back.
Limits and pitfalls
The notice does not tell you that something went wrong; it tells you the application cannot prove that nothing did. That distinction is the whole point of the wording.
Notices live in this window's memory. Closing the application clears them, which is why acting on them before closing matters.
A malformed payload is dropped rather than shown: a notice is only accepted when the connection, notice identifier, account and message are non-empty strings and the source and severity match exactly. This is a strictness guarantee, not a claim that every real problem produces a notice.
A related banner exists for automatically adjusted protections; it reports a gap that no modification corrected, and an order the application adopted without having placed it. It does not close on its own either.
Related pages
This page in other languages
Frequently asked questions
- Does acknowledging a notice cancel anything at the broker?
- No. The button removes the entry from this list and nothing else. Any order or position you found at the broker has to be handled at the broker.
- Why does the banner have no close button?
- Because a dismissable banner would let an unresolved uncertainty disappear with one reflex click. The only exit is the acknowledgement that names the account you checked.
- Will the notice come back after I acknowledge it?
- Not that one. A later event may emit a new notice about the same account, which is a separate uncertainty and deserves its own check.