> ## Content Index
> Fetch the complete content index at: https://blog.algorover.ai/llms.txt
> Use this file to discover other available public pages before exploring further.

# Your one-minute strategy ran all night. Why are there still no trades?
- URL: https://blog.algorover.ai/one-minute-strategy-no-trades-chat-en/
- Published: 2026-11-10T15:57:32.000Z
- Updated: 2026-11-10T15:57:32.000Z
- Description: A one-minute chart sets the observation interval. Entry rules and order outcomes determine trades. Follow market data, signals, submission and fills to locate the wait.
- Author: AlgoRover Team
- Tags: Product Tutorials, #en

The strategy says running, but it has made no trades all night. Follow four stages: fresh market data, entry signals, order submission and fills. One-minute candles set the observation interval; a trade still needs its conditions to pass and its order to execute. Which stage is holding this run up?

These are separate checks when a trading bot is not placing orders. In AlgoRover's runtime monitoring, match the current revision and instance first, then follow one record through the process. That separates waiting for conditions from a stopped data feed or an order problem.

## Check the running instance and latest candle first

User · simulated conversation

I selected a one-minute strategy and waited all night. It says running, but positions and orders are both zero. Is that normal?

AI

Check when the instance started and the timestamp of its latest processed candle. Then inspect the market-data connection.

Complete any pending startup confirmation for that instance. If it is running and processing fresh data, inspect entry signals next. Instance status and submitted orders describe separate stages.

**Turn “started” into a specific runtime record**

An installed strategy, a completed backtest and a running instance refer to separate operations. Match the instance name, revision and start time before inspecting the rest.

## Do one-minute candles imply a trade every minute?

User

The candles are current. If the strategy checks every minute, why hasn't it bought?

AI

Inspect what it checks. A strategy may require a local low, a sufficient price decline and a volume condition together. Each new candle is another evaluation of those rules.

A local-low rule may need several later candles for confirmation. Trading hours, warm-up and cooldown can also delay entry signals even on a one-minute interval.

User

Would asking which condition is missing be more useful?

AI

Ask for the current rules, latest evaluation time, each condition's result, and any trading-window or risk-control restriction.

**Make waiting a condition checklist**

Think of a cart facing several gates. Checking the route more often does not open the gate whose condition is still false. Inspect those results before changing the rules; test changes as a separate revision.

![A cart is blocked by the closed volume gate while the price and trading-hours gates are open.](https://storage.ghost.io/c/6d/bb/6dbbb7cc-1f93-4cd3-8d75-e3c2cfce055f/content/images/2026/11/entry-conditions-explain-en.png)

One closed condition blocks entry. Checking more often does not open the gate.

## Why can an entry signal exist without a filled order?

User

The log contains a buy signal, but the account still has no fill.

AI

Follow that signal forward. Was an order submitted? Did the exchange accept it? Was it filled, partly filled, canceled or rejected?

With no submission, check positions, cooldown and risk controls between the signal and order. For accepted but unfilled orders, inspect price, validity and cancellation records. For a rejection, retain the exchange response and check minimum order size, quantity increments, margin and permissions.

| Observed record   | Next check                                  |
| ----------------- | ------------------------------------------- |
| Fresh market data | Each entry condition's result               |
| Signal generated  | Order submission and blocking rules         |
| Order accepted    | Fill, partial fill, cancellation or expiry  |
| Order rejected    | Exchange error and account/order parameters |

**Follow the same record forward**

No fill is an outcome that can arise at several stages. Link the data, signal, submission, acceptance and execution to identify the stage that needs attention.

## Ask AI to inspect runtime logs, signals and orders

User

Ask AI with this promptCopy

Inspect the current strategy revision and instance start time. Check the latest processed candle, trading window, warm-up and cooldown. List each condition's result at the most recent entry evaluation. Then check recent order submission, acceptance, fills or rejections and explain which stage is currently waiting or failing.

AI

This ties the answer to the current instance and specific records. An unmet condition explains the wait; a stale feed or rejection points to a narrower next check.

**Evaluate trade frequency against the strategy's goal**

If the goal is more trades, compare completed trades per day, fees, holding time, return and drawdown in a separate experiment. First establish what the current rules are doing.

## A running trading bot with no trades: common questions

### What should I check first when a trading bot is not placing orders?

Match the running instance and latest market-data time, then inspect entry conditions, the trading window, position limits and submission records. If an order exists, follow its acceptance and final execution status.

### Does a one-minute strategy always trade more than a five-minute strategy?

Trade frequency depends on the full rules and test period. Hold other settings constant, then compare completed trades, fees, holding times and maximum drawdown.

### Should I use the same checks for a demo account with no orders?

Start with data, signals and orders, and verify the demo account, exchange environment and contract. If the backtest traded, compare revisions, data periods and initialization with the running instance.

### How do I verify that an AlgoRover strategy is still running correctly?

Check its revision, start time and latest processed candle in runtime monitoring, then inspect recent signals and orders. Process status, fresh data and actual fills each need their own check.

## Read next

[Why a paper trading order can stay submitted](https://blog.algorover.ai/why-paper-trading-order-stuck-submitted/)

[Verify the demo and live trading environment](https://www.algorover.ai/en/help/demo-and-live/?ref=blog.algorover.ai)

[Explore AlgoRover Live](https://www.algorover.ai/en/live/?utm%5Fsource=edgepilot%5Fblog&utm%5Fmedium=article%5Fcta&utm%5Fcampaign=one-minute-strategy-no-trades-chat-en&utm%5Fcontent=article%5Fbody%5Ftool)

### Sources

[Cryptohopper: why orders are not being placed](https://support.cryptohopper.com/en/articles/9013158-why-aren-t-orders-being-placed?ref=blog.algorover.ai)