Deals not closing at TP in open source, I think

Bug Reports
1

Something odd is going on with the open source platform that I’m not sure how to troubleshoot or what to grab screenshots of to describe. It feels like it isn’t closing deals when they hit their TP until the docker image is restarted, and then it catches up but ignores them again until the next restart.

For example, here is a screenshot after running overnight about 8hrs, and it’s the same 21 cents from the last restart.

image
image833×405 34.9 KB

Here are some trades that should have closed at 2% profit:

image
image1669×573 132 KB

I just restarted the Docker container, and now the trades have all closed and taken profit.

image
image839×395 34.6 KB

image
image1670×567 21.5 KB

And it will do that until the next restart, etc. I’ve got PRICEROLE=all in the environment file, and I’ve tried it on both my laptop and desktop with similar results.

Any ideas? Any screenshots or details I can send to help troubleshoot?

Thanks!

2

Hello! Thank you for reporting this issue. We have received your bug report and will update you shortly.

To help us investigate this further, could you please provide the deal IDs for the trades you mentioned? This will allow us to look into the specific details of these deals. Thank you!

3

What is TP trigger?

4

image
image503×342 10.1 KB

image
image500×393 13.3 KB

image
image508×353 16.7 KB

image
image502×377 17 KB

image
image500×384 12.9 KB

image
image503×361 12.9 KB

Here’s a bot setting file if that helps:

Plankton Long.json (15.5 KB)

5

Could be a problem with user stream container. It might lost a connection to coinbase and not able to fix it by itself. You don’t need to restart whole system, you can restart user stream container, bot should perform a check after this container restarted.

6

It does it when creating a whole new container for the first time though, as I’ve tried twice on my laptop and once on my desktop, and the latter two were brand new setups from scratch. They are also all paper accounts so far, not live ones; I’m not sure if that’s an insight.

7

Ah ok, I though it was live.
Than the problem in price connector. Try to restart it should feed tickers to paper trading again

8

But that’s the thing, restarting only fixes it until the next restart.

9

It seems to be the stream-1 service. I restarted that and the total profit jumped instantly, but restarting bots-dca-1, indicators-1, exchange-connector-1, paper-trading-1, price-connector-1 individually didn’t produce any updates. Not until I got down to stream-1 service.

I’ll restart that service again in a few hours.

10

Probably something wrong with price stream connector from your side.
Can you send a logs of it?

11

I waited 4 hours, but this time restarting the bots-dca-1 service got trades to close.

The price-connector-1 log is huge, but this repeats a lot in it:

price-connector-1 | 2025-09-16T20:29:08.381Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:08.580Z | BINANCECOINM ticker opened coinm wss://dstream.binance.com/stream
price-connector-1 | 2025-09-16T20:29:08.585Z | BINANCE error: main {}
price-connector-1 | 2025-09-16T20:29:08.981Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:09.165Z | BINANCE error: main {}
price-connector-1 | 2025-09-16T20:29:09.551Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:09.741Z | BINANCE error: main {}
price-connector-1 | 2025-09-16T20:29:10.076Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:10.306Z | BINANCE error: main {}
price-connector-1 | 2025-09-16T20:29:10.714Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:10.874Z | BINANCECOINM ticker opened coinm wss://dstream.binance.com/stream
price-connector-1 | 2025-09-16T20:29:10.880Z | BINANCE error: main {}
price-connector-1 | 2025-09-16T20:29:11.285Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:11.457Z | BINANCEUSDM ticker opened usdm wss://fstream.binance.com/stream
price-connector-1 | 2025-09-16T20:29:11.460Z | BINANCECOINM ticker opened coinm wss://dstream.binance.com/stream
price-connector-1 | 2025-09-16T20:29:11.465Z | BINANCE error: main {}
price-connector-1 | 2025-09-16T20:29:11.845Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:12.046Z | BINANCE error: main {}
price-connector-1 | 2025-09-16T20:29:12.392Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:12.623Z | BINANCE error: main {}
price-connector-1 | 2025-09-16T20:29:13.002Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:13.187Z | BINANCE error: main {}
price-connector-1 | 2025-09-16T20:29:13.543Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:13.761Z | BINANCECOINM ticker opened coinm wss://dstream.binance.com/stream
price-connector-1 | 2025-09-16T20:29:13.763Z | BINANCE error: main {}
price-connector-1 | 2025-09-16T20:29:14.151Z | BINANCEUS ticker opened main wss://stream.binance.us:9443/ws/stream
price-connector-1 | 2025-09-16T20:29:14.333Z | BINANCECOINM ticker opened coinm wss://dstream.binance.com/stream
price-connector-1 | 2025-09-16T20:29:14.337Z | BINANCEUSDM ticker opened usdm wss://fstream.binance.com/stream
price-connector-1 | 2025-09-16T20:29:14.346Z | BINANCE error: main {}

Probably due to my USA IP address again. Hehe

12

Could be due to errors in price connector.

I added a new variable PRICE_CONNECTOR_EXCHANGES. You can specify allowed list of supported exhcange. You can coinbase or binanceus,coinbase. Both should work from your IP.

13

Thanks, I’ll try this out!

I’m stuck down another rabbit hole testing it today though. Apparently bitnami changed some things overnight regarding mongo and this catalog has been deprecated:

image
image1115×628 17.1 KB

14

This looks relevant, and matches the time window I’m experiencing:

15

I got up and running by making three small changes to docker-compose.yml:

image: ‘docker.io/bitnamilegacy/mongodb:7.0’
image: ‘docker.io/bitnamilegacy/redis:7.2’
image: ‘docker.io/bitnamilegacy/rabbitmq:3.13’

The databases had changed enough that it was easier to start over than to try migrating data, I didn’t have anything I cared about on the paper account.

So I’m up and running again with PRICEROLE=all and PRICE_CONNECTOR_EXCHANGES=coinbase and I’ll let it run overnight and see how things go.

Thanks again!

16

Thanks.

I have updated from binami to bitnamilegacy

17

No deals closed overnight until restarting sadly.

image
image1668×1003 127 KB

image
image1663×591 193 KB

After restart:

image
image1663×1006 166 KB

image
image1669×591 197 KB

18

Also, I’m not sure if this is related, but I think this all has to do with the “required change” feature of the take profit and how it uses limit orders or something? I say that because “mini plankton” bots worked fine with open source, even when I ran a paper account using PRICEROLE=candle instead of PRICEROLE=all. And one of the changes we made with “big plankton” bots was switching the take profit to the required change feature. Now even with PRICEROLE=all the trades are not closing on open source without a restart, but they do work on the subscription platform.

HOWEVER, I observed this today on my subscription platform. On my real, live account I’m still running “mini plankton” and I do not have all of my funds on each bot tied up in limit orders. The IN LIMIT column for each balance is $0 for mini plankton. But my paper account is running “big plankton” with the required change feature for take profit and most of my funds ARE tied up when I check the IN LIMIT column for each balance, and this surprises me because these should be “ghost orders” when it comes to the exchange. The funds should not be tied up and be available for use to my understanding. Here are two screenshots of my real and paper accounts on the subscription platform to show what I mean. The biggest difference is the “required change” feature of take profit. I wonder if this provides any insight into the open source platform not closing the trades?

image
image1670×989 144 KB

image
image1668×991 161 KB

19

As I understand previousl TP was not a limit order, but now it is.
It means that paper working fine with market orders, but something wrong with limit.

There are 3 possible reasons:

  1. paper did not received live tickers
  2. paper did not sent order update
  3. bot did not received order updates

2 actually never happened in our history.
3 possible, but we never had this problems actually (is user stream working fine)

I assume the problem with live tickers update.
To debug

  1. Expose port of redis container
    add this to your container definition
    ports:

    • 6379:6379

  2. Install redis insight

  3. Check pub/sub output

    redis
    redis2586×780 297 KB

    You can subscribe to channel trade* and check the output. If its empty than problem with connection to coinbase, if it has data than I will think about how we can debug it further.

20

  1. Will TP with “required change” always be a limit order, is this a design choice or request? We’d like them to be ghost orders with plankton, as I think previous TP methods are. But I’m not sure if this is a bug or design choice based on user feedback?

  2. I got redis insight connected and I’m subscribed to trade* under the pub/sub output. I see a LOT of activity and data flowing by the second. I’ve had it running for several minutes and still seeing data flowing. Here’s a quick screenshot:

image
image1843×992 124 KB

I’m headed out of town until this evening, but I’ll check when I get home and see if any trades closed while I was gone, but I don’t think they will. :wink:

Hope this helps troubleshoot, thanks again!