Reference · 7 minute read
Get unstuck: common questions and recovery steps
Find the next step for connection problems, blocked approvals, uncertain orders, empty results, and missing history.
Published by BrokerBridge · Guide content reviewed
Start with the visible message
Note which screen you are on, the selected account, and the exact message. Separate four questions: can the app reach the AI provider; can it reach the broker; is the requested action permitted; and is current data available? A failure in one does not prove all four failed.
- Read the message beside the disabled control as well as any temporary notification.
- Keep a note of the time, action, account mode, and result. This makes an intermittent problem easier to explain.
- If you might already have sent an order, use the uncertain-order steps below before retrying.
- After changing a setting, wait for its saved confirmation and recheck its state. Editing a field alone does not establish a saved connection.
Chat cannot answer or a model is unavailable
Before you start: Open Settings → Models & Credits and keep the exact error message available. Never include an API key in a support report.

- Check the model: this reply came from Local Demo, not a connected AI provider.
- A workflow message does not mean you must place a trade. Read the glossary or change to an available connected model for open-ended questions.
- The reply states that no order was created. When an action outcome is uncertain, check orders and holdings before retrying.
Check Models & Credits
Open the model name at the top of the window. Its State reads Ready, Unverified, Stale, Attention, Down or Checking. Unverified or Stale means it has not answered recently: send a short message or use Test Connection. Then read the provider, access, credit and limit messages in Models & Credits.
You should see: The problem is identified as access, sign-in, credits, limits, unsupported input, or another specific failure.
If you get stuck: Do not paste credentials into Chat or a problem report. Use the dedicated connection controls.
Use the recovery for that cause
Complete sign-in, retry access verification, or choose an available compatible model as appropriate. For an attachment, check Vision or PDF support separately.
You should see: The provider reports readiness and a small ordinary text request receives a response.
If you get stuck: If Local Demo is selected, open-ended research is not available through an AI model. Use its supported local workflow or connect a verified model when available.
- Open Models & Credits (in the desktop app)
The broker is disconnected, or account identity is unclear
Open Broker Accounts and inspect the selected trading account. For Interactive Brokers, ensure the selected IB Gateway or Trader Workstation application is open and signed in. Compare its API Socket port with the preset or manual settings, then use the connection test. Read the account and mode returned by the test.
Open Brokers at the bottom of the left sidebar to see Broker connections. State reads Ready, Paused, Attention, Down, Checking or Disconnected. Execution reads Connection ready, Read-only, Not ready or Execution halted. Read-only means Read-Only API is still on in IB Gateway or TWS. Not ready means the account is not verified or the broker link is not ready yet. On Dashboard, System Health shows limited in amber when something works only in part, is paused on purpose, or needs a setting you can fix; read its detail line.
For NinjaTrader, the badge must read NT8 connected and the bound account name must match your intention. UNVERIFIED means NinjaTrader or its link is not running or not installed; see the setup guide. A connected application can contain multiple accounts. If the account name, local/paper/simulated/live label, or plan destination conflicts with your intention, resolve that mismatch before any order.
If balances load but orders are refused, inspect the reported permission or read-only status. On Interactive Brokers, Read-Only API must be off in the IBKR application before any order can be sent. A successful account read is not a successful order-permission test. Do not remove a protection or change an account mode simply because a connection indicator is green.
- Open Broker Accounts (in the desktop app)
- Read the setup guide →
Approve is unavailable, or the plan is refused
| Message concerns… | Next step |
|---|---|
| “Complete trading setup first” or a named setup step | Follow the link in the message. It names what is missing: account setup, a selected account, the risk disclosure (trading agreement), AI access, or a broker that is not ready. Ticking checklist items does not unlock approval. |
| Activation or access | Connecting a broker may need a Desktop Activation Code from your dashboard at brokerbridge.tech. The Local account needs none. |
| Account or destination | Verify this plan's account in Broker Accounts and read its current destination. |
| Missing quantity or prices | Review the plan and supply the missing details through its supported edit or draft workflow. |
| Stale quotes or missing market data | Use the displayed refresh/review action and check the data source. Resolve any subscription message at the provider. |
| A risk limit | Read which limit failed and why. Reassess the plan rather than automatically increasing the limit. |
| An expired or changed plan | Refresh or request a new draft, then review its current terms. |
| Real-money confirmation | Typing LIVE once lets later orders to that same live account go out with one click for 8 hours, from any screen. It ends sooner after a pause, a restart, or an account or connection change, so you may be asked again. Closing, trimming or tightening a stop never needs LIVE. Loosening a stop or moving a target still does. |
| “Execution is paused by an operator hold” or “…while the backend finishes restarting” | An operator hold means someone chose Pause new execution in Execution at the top of the window. It stays until someone chooses Resume persistent pause. A restart pause ends by itself once BrokerBridge finishes restarting; then review and submit again. Resuming is a deliberate decision. |
| “Your daily loss limit was already hit earlier today” or an account loss limit | This is not the execution pause, and Resume does not clear it. The daily loss check in Settings → Risk & Trading keeps new trades blocked until the next trading day, even if prices bounce back. An account loss limit blocks new positions only while the account is at or past it, so a bounce can reopen trading. Closing or trimming what you hold still works. Review the limits in Settings → Risk & Trading. |
| “Remind me to test the emergency stop” | A reminder only. It never blocks an order. When convenient, use Test the emergency stop under Execution at the top of the window. It runs only on a paper or simulator account. |
An order was sent, but I cannot tell what happened
Before you start: Stop sending new instructions for this order while you determine its outcome. Keep the original account and order details available.
A limit order can remain working because the market has not offered an acceptable execution. A partial fill leaves a holding and may leave a remaining order. Cancelling that remainder does not close the filled portion. Use the order guide before changing either one.
Do not submit it again yet
Keep the account, time, symbol, quantity, and order identifier. Read the status shown, such as Submitted, Working, Partially filled, Status unknown or Needs review.
You should see: You avoid treating a timeout as an automatic failure.
If you get stuck: A second request can become a second order if the first was accepted.
Check both orders and holdings
Inspect the plan's status in Chat tools → Plans or Dashboard → Trade Plans, and the holding in Dashboard → Open Positions. For broker trading, inspect the broker application's orders and positions for the exact account and contract. Refresh after connectivity recovers.
You should see: A confirmed status or actual holding explains the outcome.
If you get stuck: If sources disagree, retain the details and report the outcome as unconfirmed. An empty filtered view is not cancellation proof.
A position shows STOP NOT FILLED or held by BrokerBridge
- STOP NOT FILLED means your stop-limit triggered, but the price moved past its limit, so nothing filled. The position is still open and unprotected.
- BrokerBridge only warns you; it does not trade for you. Choose Close now on that position to open the close confirmation, or leave the limit working.
- PLAN INVALIDATED means the price reached the plan's own invalidation level. It is also a warning only, with the same Close now choice.
- For crypto at Interactive Brokers, the stop and target are held by BrokerBridge on this computer, not by the broker. They work only while BrokerBridge is running and connected, and only while trading is not paused.
- If that badge offers Re-arm, the stop is not active. Choose Re-arm to restore the stop you approved, or watch the position in your broker application.
My scanner, playbook, or Arena shows nothing
First distinguish no match from no successful run. In Scanners, inspect the run result, skipped symbols, data source, and error message. In AI Playbook, inspect Activity, source freshness, the selected output behavior, and the schedule. In Arena, inspect the run state, decisions, competitor availability, and any model-access message.
A research-only playbook may produce a brief without a trade plan. A saved scanner waits for Run unless another explicit workflow schedules work. An Arena competitor may choose to hold cash. Those outcomes differ from unavailable data or a failed check. Use the explanation accompanying the result before changing rules.
- Open Playbook Activity (in the desktop app)
- Learn Scanners and Arena →
A trade is missing from Journal
- Journal starts with your active account only. Tick the right account under Journal accounts, and choose the intended Source.
- Widen Range and check Timezone. Confirm Start is on or before End.
- Use Ledger to inspect underlying history; use Dashboard for a holding that remains open.
- Read collection coverage and import warnings. A source error or incomplete coverage is different from no activity.
- Compare the exact account, order identifier, and fill time with the broker record. Report the missing record with those details when recovery does not resolve it.
- Open Journal Ledger (in the desktop app)
Make a problem easy to investigate
Open the status menu (ⓘ) at the top of the window, then Help → Report a problem. Settings → Advanced → Diagnostics shows more detail. Include what you were trying to do, the smallest repeatable steps, what you expected, what appeared instead, and the time and timezone. Include the app version, shown next to the BrokerBridge name in the left sidebar. For account problems, say whether it was Local, paper or live, and hide private account details in shared screenshots.
- Quote the exact error instead of only saying “it does not work.”
- For uncertain orders, include the order identifier and whether the broker reports a working order or holding.
- For missing data, include the symbol, source, timeframe, and timestamp shown.
- Do not include passwords, API keys, sign-in codes, or private authentication links.
- Open Diagnostics (in the desktop app)
Continue in the website manual
These online references extend this lesson with existing setup instructions and technical detail. They need an internet connection. The downloadable guide keeps all beginner lessons available offline.
See this workflow in BrokerBridge
Explore the matching tool, or try an illustrative browser example. Use this lesson to understand the controls before working in your own account.