Safety Orders not triggering after latest update on ComboBot

pagani.a · October 14, 2025, 10:27pm

Environment:

– Stack: Gainium Docker (self-hosted)

– Exchange: paperBitget

– Bot ID: 68ee2c447dd6f950b1e2df31

– Pair: COQUSDT

– Context: Paper mode

Description:

After the recent Gainium update, my combo bot stopped placing Safety Orders (CMB-SO-…).

The Base Order executes correctly and the Minigrid is created, but no DCA/SO orders are sent even when the price moves far below the configured step percentage.

The same configuration was previously working before the update.

Expected behavior:

Safety Orders should trigger automatically when the price drops below the configured step threshold.

Observed behavior:

– Base order and minigrid creation OK

– No CMB-SO-… entries in logs

– No entries in orders collection with clientOrderId matching CMB-SO-…

Verification performed:

MongoDB checks:

– combodeals contains open deal for this bot

– orders collection has no CMB-SO- entries

– DCA parameters confirmed (useDca:true, step:2.5, ordersCount:17, activeOrdersCount:1)

Amia · October 14, 2025, 10:27pm

Thank you for reporting this issue. We have received your bug report regarding Safety Orders not triggering on your ComboBot and will investigate it shortly. You mentioned the Bot ID: 68ee2c447dd6f950b1e2df31, which is helpful. We will update you as soon as we have more information.

maksym.shamko · October 15, 2025, 7:21am

I don’t know where did you got that. The prefix for combo DCA order is CMB-RO, grid - CMB-GR, start - CMB-BO

pagani.a · October 15, 2025, 4:24pm

It was a typo error. the CMB-RO is not beign executed. do you need any specific log?

Thanks,

Andrea.

maksym.shamko · October 15, 2025, 5:13pm

Ok maybe I understand you wrong, so question is order not filled or not placed?

pagani.a · October 16, 2025, 8:22am

The order is not filled for all bots running.

maksym.shamko · October 16, 2025, 8:34am

There was a problem with paper few days ago.
I have built image for the latets version. Please pull fresh compose file.

If problem not gone, probably the reason in price connector service.

pagani.a · October 16, 2025, 6:38pm

Maksym,

I updated the whole compose file and still Safety orders are not being used when the price hit them.

Andrea.

maksym.shamko · October 16, 2025, 7:43pm

Probably something wrong with you price connector. Ensure that price role set to “all”

pagani.a · October 17, 2025, 3:13am

Nothing change..

#websocket-connector
PAPER_WS=ws://paper-trading
PRICEROLE=all

maksym.shamko · October 17, 2025, 7:02am

Please check PRICE_CONNECTOR_EXCHANGES env values. if it exists, and if so what value.
Try to set PRICE_CONNECTOR_EXCHANGES=bitget and run
docker compose up -d price-connector

pagani.a · October 18, 2025, 1:39pm

Maksym,

nothing change, i’m attaching also a view for your better looking, it is not working Safety order in ComboBots neither on Trading Bots.

maksym.shamko · October 18, 2025, 1:41pm

Ok, its realy hard to say.
please attach your .env, logs of paper container, price container

pagani.a · October 19, 2025, 9:57am

gainium-app_bots-combo_1.filtered.log.txt (42.4 KB)

gainium-app_price-connector_1.tail300.log.txt (28.3 KB)

gainium-app_price-connector_1.log.txt (58.4 KB)

gainium-app_paper-trading_1.log.txt (7.3 KB)

gainium-app_bots-combo_1.tail300.log.txt (39.3 KB)

gainium-app_bots-combo_1.log.txt (186.5 KB)

env.original.txt (870 Bytes)

maksym.shamko · October 19, 2025, 3:00pm

Ok, I will take a look tomorrow

maksym.shamko · October 20, 2025, 7:48am

Do you have user stream service deployed?
I can see that bot not receiving real time updates.

pagani.a · October 20, 2025, 10:17am

Yes — the user stream service is deployed and currently healthy.

Services:

- stream: gainium-app_stream_1 (port 7502)

- websocket connectors: gainium-app_price-connector_1 and gainium-app_user-update-connector_1 (v1.1.2)

- RabbitMQ: gainium-app_rabbit_1 (172.18.0.3), same Docker network as the bots

RabbitMQ status (Oct 20, Europe/Rome):

- Queues exist and have active consumers (consumers=1): comboQueue, dcaQueue, gridQueue, hedgeDcaQueue, hedgeComboQueue, usersStreamAction, candlesRequests, webhookQueue, indicatorsActions.

- Bindings are present on the “gainium” exchange for all of the above.

Bots reach RabbitMQ (DNS “rabbit” resolves to 172.18.0.3 and port 5672 is open).

In the last 2 hours, connectors show only websocket (exchange) reconnects; no AMQP errors.

maksym.shamko · October 20, 2025, 10:53am

can you attach logs from user service and redis

pagani.a · October 20, 2025, 11:07am

gainium_support_user_redis_ubuntu_20251020_110458.tar.gz.txt (78.3 KB)

Please rename and remove the .txt as the ticket system is not allowing to paste the format.

maksym.shamko · October 21, 2025, 9:47am

I have found a problem. Its a bug indeed.
Problem with paper websocket url. Fixed in latest version.
You can pull latest docker-compose, it contains also bug fixes for other services.