I started a neutral grid bot on a paper account, but it only triggered 3 orders, even though prices went down within range. Can you please check?
Hello! Thank you for reaching out and reporting this issue with your Futures Grid Bot on your paper account. We have received your report and our team will investigate this behavior. Since you have already provided the bot URL, we have the necessary details to start looking into why it only triggered 3 orders. We will update you here as soon as we have more information.
Hi @sureshbandara2 — thanks for the detailed report and the bot link, it made this much easier to pin down. You were right, the bot should have triggered more orders.
What was happening (in plain terms):
Our paper-trading engine listens to live price updates for every coin at the same time. We found a flaw where, when lots of coins were updating at once, the engine could accidentally skip the price updates for the less actively traded coins — and ARK trades far less frequently than the big pairs like BTC.
Your grid bot relies on those price updates to know when price has reached one of its grid levels. When an update got skipped, the bot didn’t “see” the price crossing a level, so it didn’t fire the order — even though on the chart the price clearly moved through that range. That’s exactly why only a few orders filled while the price slid down through your grid.
The fix:
We removed that flaw, so every price update now reaches the engine no matter how busy the other coins are. It’s already live. I’ve also restarted your ARK grid bot so it’s freshly re-armed and running normally again — it’s already placing and filling orders as expected.
Please keep an eye on it and let us know if anything still looks off. Thanks again for catching this — it turned out to affect other low-volume pairs too, so your report helped more people than just yourself. 
2 Likes
Different issue this time, it’s a dead user stream connection. I have restarted your bot to fix the immediate problem while designing a fix for detecting this and auto-fixing it if it happens again. Actually this is not even a bug, it’s what happens when the exchange silently drops the connection that the bot listen to for updates and it’s been a once in a while recurring issue over the years. We’ve tried a few things over time, hopefully this new plan finally fixes it.
1 Like
Is this issue only happening on a paper account?
I created this paper grid bot yesterday with a start trigger price.
The price reached the start point, and the bot showed it was active.
However, even though the price passed several grid levels, the bot did not trigger any buy or sell trades.
Hi @sureshbandara2 — I went through your INJ Natural bot in detail. Here’s the full picture.
The start, and the first buy
Your bot was set to start at 4.555, and it did exactly that — the moment price came down to 4.555 it activated and placed the grid (confirmed in our logs, to the second). The thing worth clarifying is that this is a neutral grid: the start price arms the grid — it doesn’t place a buy at 4.555 itself. Your first buy order sits one step lower (~4.51) and fills when price actually trades down to that level. So even with everything working perfectly, you wouldn’t see a trade right at 4.555 — you’d see it once price reaches that first grid level. (We agree the “start price” wording is misleading for this case, and we’ll make it clearer in the UI.)
The brief dip below your buy level
Price did poke down toward that first level — a quick wick to ~4.49 — before snapping straight back. Our paper simulator samples price about once per second, and that spike was fast enough to fall between samples, so it didn’t register the cross and didn’t fill. We looked at making the simulator chase every micro-wick like this, but it would add real load and cost across the platform for an edge case that’s both rare and — honestly — wouldn’t reliably fill on a live exchange either: a fleeting spike that snaps right back doesn’t always trade enough at that price to fill a resting order. So that’s one we’ve decided isn’t worth chasing.
Your account — the part actually worth fixing
Separately, your account has been hitting a known issue where the live feed that tells your bot “an order just filled” goes quiet for a while. When that happens the bot doesn’t see its fills in real time, which is what made it look stuck earlier. We’ve since added an automatic safety net that catches those fills within a few minutes — so your bots keep trading on their own now (no manual restarts needed), just with a short delay on the updates. If you check, you’ll see them filling and rolling normally.
The permanent fix — making that feed reliable so there’s no delay at all — ships as part of an infrastructure update we have planned over the next few days. Once it’s live the delay disappears entirely, and I’ll confirm here.
TL;DR: the bot started correctly; the start price arms the grid rather than buying at it; the one micro-wick miss isn’t worth the cost to chase (and likely wouldn’t have filled live either); and the slight update delay you may notice goes away with the upcoming migration. Thanks again for the detailed screenshots — they made this much easier to pin down.
It seems the issue is related to Binance keys in the old format. So the user stream won’t work at all. Please update them, Rossano made instructions you can follow here: BINANCE API update - step by step
This is a paper account. The issue looks okay now. I’ll reply if I face it again.