New Hope Crypto
Crypto Bot Connected but Not Trading: What to Check
A connected crypto bot does not necessarily have a trade to open. Connection, instrument selection, strategy conditions, order submission and execution are separate stages. Find the last stage you can confirm before changing settings or restarting the program.
This guide uses New Hope Crypto controls described in its manual and practised in New Hope Workspace. It helps answer a specific question: is the robot waiting normally, prevented from starting a new series, or encountering an order problem? Labels may differ between releases, so use the instructions supplied with your installed version.
Get free access to the New Hope Crypto training simulator
Practise the controls with educational data before connecting real funds. The team reviews access requests and emails an invitation. Software purchase is separate. Already have access? Open the Crypto setup lesson.
Start with a five-stage check
Use the same account, instrument and time window throughout the investigation. A changing BTC price on a chart, a balance on screen and a filled order prove different things. The table shows what evidence belongs to each stage.
Stage | Evidence to look for | Next check if missing |
|---|---|---|
1. Connection | Correct account and current account data; relevant log entries | Connection settings, permissions, endpoint and VPS IP |
2. Instrument | Intended instrument loaded and enabled; trading started | Instrument selection, preset and close-only controls |
3. Strategy conditions | Available decision or signal information for that instrument | Whether the strategy is waiting; ask support if the log cannot establish this |
4. Order submission | A submission entry or exchange order identifier | The preceding program message, exact time and account state |
5. Acceptance and execution | Exchange order status and actual filled quantity | Rejected, pending, cancelled or partially filled state |
Find the last confirmed stage. The diagram is an educational workflow, not a screenshot of a live account.
1. Confirm what “connected” actually proves
The New Hope Crypto manual describes Connect followed by balance and equity information. That is a useful account check. It does not, by itself, demonstrate that a new order was sent or that every required trading permission is enabled. Confirm the account identity and whether the displayed information is updating rather than relying on one earlier screenshot.
Read access and trading access are distinct. For example, OKX documents separate Read, Trade and Withdraw permissions. Seeing account data is therefore not sufficient evidence of order-placement permission. Review the relevant exchange settings without sharing secret keys or enabling withdrawal access as a troubleshooting shortcut.
Also check that the configured market and environment match the account you intend to use. Spot, derivatives, demo and live are not interchangeable labels. Do not switch account or position modes simply because another tutorial uses them. Follow the requirements for your release and exchange connection. Our crypto API permissions guide covers that separate setup task.
2. Check the instrument and trading controls
In the documented New Hope Crypto workflow, connecting the account is separate from starting trading and enabling instruments. Confirm the intended symbol is loaded, its row is enabled and the trading control is in the intended running state. Check the preset against the actual instrument instead of assuming that a similar ticker refers to the same contract.
The manual also describes an initial check of instruments, open positions and trading increments. Let that process complete and read any messages it produces. Repeatedly pressing Start does not reveal which check failed. Record the state once, then work through the specific message.
Check the account-level closing mode and the instrument-level closing setting. These controls are intended to stop new trading series while handling existing positions. A robot in this mode may be connected and working without opening new series. Do not disable the mode automatically: first establish whether it was deliberately enabled and review the positions it is managing.
3. Distinguish waiting for a signal from an unexplained gap
A strategy does not have to trade every minute or react to every visible price move. An enabled instrument and an active connection do not establish that its entry conditions have occurred. Compare the configured strategy, available signal information and the instrument's recent messages.
If the log does not expose its decision state, label the cause not yet established. An empty trade list alone cannot distinguish a normal wait from a missing input or configuration problem. Send the observation to the team rather than claiming that the robot definitely had no signal.
Keep the settings unchanged while collecting the initial evidence. Raising risk or adding instruments just to make a trade appear changes the conditions you are trying to diagnose. A successful diagnosis identifies a stage and cause; a new position on its own does not.
4. If an order was submitted, follow its actual status
Look for the instrument, time, request result and order identifier where available. Then compare them with the exchange's order records for the same account and market. Check open orders as well as trade history: a limit order waiting in the book is not a completed trade.
Bybit explicitly distinguishes an accepted order request from its subsequent order status. Its API acknowledgement is asynchronous. For a user, the practical point is simple: a successful request response is not a fill confirmation. Record the filled quantity and final status, including partial fills or cancellations.
If a request timed out, do not assume it failed and immediately repeat it. Establish whether the exchange already has the order. If a rejection is recorded, use its exact code and message; the order rejection guide explains how to organise that evidence.
A small calculation can reveal an order-size problem
Consider a fictional instrument with a price of 2.20 USDT, a quantity increment of 0.1 and a minimum order value of 10 USDT. A proposed quantity of 3.4 respects the increment, but its value is only 3.4 × 2.20 = 7.48 USDT. Passing the quantity-step check does not mean the order passes the minimum-value check.
These are teaching numbers, not current exchange rules. Binance explains separate filters for price, quantity and notional value. Use the current rules for the exact instrument and market. Identify the mismatch, then review the preset with support; do not increase risk merely to force an accepted order.
Prepare a useful support report
One short incident report is more useful than “connected, no trades”. Include the following without exposing account secrets:
New Hope Crypto version, exchange and demo or live environment.
Exact instrument and market type, plus the preset or settings reference.
Observed time window and timezone, and the last trade time if known.
Connection, trading, instrument and closing-mode states.
The relevant log messages and any order status or rejection code.
Whether open orders or positions exist, and what changed before the issue.
Crop screenshots to the relevant panels and remove API keys, secrets, passphrases and unrelated personal information. Do not delete logs or program folders to make the screen look clean. If the problem began after moving the robot or restarting a VPS, note that event and use the restart and recovery checklist before further changes.
Practise the controls before troubleshooting a live account
The New Hope Workspace Crypto trainer lets you explore connection, instrument selection, risk settings, starting and stopping, positions, closing mode and the log using a simulated account. It does not connect to an exchange or test your actual API credentials. Practising there helps you describe the live program's state more precisely.
Request free Crypto learning access · Explore New Hope Crypto
Already using the software? Send the incident details to the New Hope team. The goal is to find the last confirmed stage and resolve the specific cause, without guessing at settings or creating unnecessary trades.
More articles
