Skip to main content
This screen is part of the Vole Bot package.
Entry Monitor is a single feed of every signal your bots have seen, across all of them, and what happened to each one — whether it turned into a trade, was turned away, timed out, or is still being evaluated right now. It’s the cross-instance view of the same waiting-signal information you’d otherwise have to check bot by bot. A signal can show up here as a waiting (“pending”) row when a bot’s policy has the Wait Before Entering rule switched on. That rule is explained further down this page. The other pre-entry filters are described under Execution Policies.

Summary

At the top, a row of counters shows how many signals are pending right now, plus how many fired, were rejected, or timed out recently, and an overall share of signals that didn’t lead to a trade. Below that, a chart shows the most common reasons signals get turned away, described in plain language.

Filtering the feed

You can narrow the feed by instance, by outcome (pending, fired, rejected, timeout, or refused), by broker, and by date range.

Reading a row

Each row summarizes one signal’s life: when it appeared, which bot produced it, which side it was on, its current state, why it ended the way it did, and how long the whole thing took. Clicking a row opens a step-by-step account of how the bot evaluated that signal over time. A link from the row also takes you to the instance’s own chart.

Refused signals

A Refused row is a signal that an entry rule turned away the moment it appeared, before any waiting began. Two rules produce these rows: Skip Spike-and-Fade Signals, and the two entry choices of the Volume Spike Rule (Don’t enter on a spike and Only enter on a spike). Clicking the row shows why the signal was refused.
  • For Skip Spike-and-Fade Signals, the details show the signal candle the rule judged, which is the candle the signal came from. They compare the length of the wick against your trade with the size of the candle’s body, and show your limit.
  • For the Volume Spike Rule, the details show the signal candle’s volume as a multiple of the recent average, and the spike size you set.
The Refused filter lists only these rows.

Canceling a stuck signal

If a signal is still pending and you no longer want it to turn into a trade, you can cancel it by hand from the instance’s own detail screen. Canceling turns it into a rejected signal — it only affects that waiting signal and never touches an open position — and it can’t be undone; if the same condition happens again, it starts over as a new signal.

Wait Before Entering

Wait Before Entering is the rule behind the waiting rows on this page. When your strategy signals, the bot does not open the trade straight away. It holds the signal, rechecks the market every 30 seconds, and opens the trade only when your conditions are met. If they are not met in time, the signal is dropped. Use it to avoid entering a move that is already going against you.

When it acts

  • It only works with Bar Close entry timing. The policy and instance forms refuse to save the rule with Validated or Smart, and show a yellow warning icon beside the rule’s (i) with the message “Wait Before Entering only works with Bar Close entry timing.” A setup saved earlier with that combination still runs, but the rule is ignored and the bot enters by that timing as if the rule were off. See Execution Policies for the entry timing choices.
  • When the signal candle closes, the bot holds the signal instead of ordering at once. The signal appears on this page as a waiting row.
  • Your other entry checks come first. If Skip Spike-and-Fade Signals or a similar check refuses the signal, the signal never starts waiting. The usual entry checks are asked again when the order is finally placed.
  • Every 30 seconds the bot checks your conditions. When they are met, it places a market order and the row becomes Fired.
  • The wait ends without a trade in three cases. The signal times out when Give up after (candles) closed candles have passed after the signal candle. The signal is rejected when your strategy signals the other direction, or when the “no move against you” test fails. You can also cancel it yourself, as described above.
  • The rule’s settings are copied when the signal appears. Editing the policy later does not change a signal that is already waiting.
On the policy and instance forms, the rule is listed under Pre-Entry Filter in the Pro Exit Modules list.

The five ways to place the order

When to place the order picks how your conditions are combined.
  • All conditions true at once. Every condition must hold in the same check.
  • Price crosses your level. You need a Price condition. The order is placed when the price crosses your level between one check and the next, in the direction the comparison says: is above means crossing up, is below means crossing down. The first check compares with the price at the signal. Any other conditions are only recorded.
  • Enough conditions agree (weighted). You give each condition a weight. The order is placed once the weighted share of conditions that hold reaches Score needed to enter (0–1). A condition with weight 0 has no say in the vote and is only recorded.
  • Conditions happen in order. Only Step 1 is checked at first. When it holds, Step 2 is checked, and so on. The order is placed when the last step holds. A step that has held stays passed.
  • No move against you during the window. The bot compares the closing price of each one-minute candle with the price at the signal. If any close moves against your direction by more than Allowed move against you (%), the signal is rejected. If the whole Watch window (seconds) passes without that, the order is placed. A move exactly equal to the limit is not a breach.

Settings

Worked example

The numbers below are made up to show how the rule works. They are not typical or expected results. Your policy uses Bar Close entry timing and Wait Before Entering with Conditions happen in order. Step 1 is RSI is above 55. Step 2 is Price is above 1005. Give up after (candles) is 2. Your strategy signals long on a candle that closes at 1000. If the second candle after the signal had closed before Step 2 held, the signal would have timed out and no trade would have opened. Two shorter examples with the other modes:
  • Enough conditions agree (weighted) with three conditions, weights 2, 1 and 1, and Score needed to enter (0–1) at three quarters. The first and second conditions holding gives three out of four, which is enough. The first condition alone gives two out of four, which is not.
  • No move against you during the window on a long signal at 1000, with an allowed move of 1 percent. If any one-minute close during the window is below 990, the signal is rejected. If none is, the order is placed when the window ends.
A timeline of checks every 30 seconds after a long signal. Step 1 fails at 0:30 and 1:00 and passes at 1:30. Step 2 fails at 2:00 and passes at 2:30, and the order is placed at market. A bar below shows that the wait ends after the set number of candles if no order was placed.

The checks in the worked example. Made-up numbers.

Good to know

  • Only whole, closed candles count toward Give up after (candles). The signal candle itself does not count.
  • If the bot restarts, waiting signals are picked up again. A signal whose waiting time ended while the bot was stopped is timed out, not traded.
  • A backtest and a preview on past data do not replay this rule, because they have no market to recheck between candles. A live run can take fewer trades than they show. See Run Backtest.