The POST ONLY BUY order had been rejected even if the price is 2 ticks bellow the market.

hi
The is a strange situation with the POST ONLY orders for SOLUSDT.

On 2025-04-21 10:10:15.473 the BID/ASK for SOLUSDT was 139.91/139.92
The server rejected the order BUY @139.89 SOLUSDT with the exception. See the log records, please.

2025-04-21 10:10:15.475 | INFO | TP updater for SOLUSDT -0.62 | c.b.c.f.client.utils.RequestHandler - POST https://fapi.binance.com/fapi/v1/order?symbol=SOLUSDT&side=BUY&price=139.89&type=LIMIT&quantity=0.62&timeInForce=GTX&newClientOrderId=TP_SOLUSDT&reduceOnly=true×ta
mp=1745230215474&signature=774ce150e2d9*******
2025-04-21 10:10:15.531 | ERROR | TP updater for SOLUSDT -0.62 | BinanceApiClient.BinanceBroker - placeLimitOrder failed
com.binance.connector.futures.client.exceptions.BinanceClientException: {"code":-5022,"msg":"Due to the order could not be executed as maker, the Post Only order will be rejected. The order will not be recorded in the order history"}
at com.binance.connector.futures.client.utils.ResponseHandler.handleErrorResponse(ResponseHandler.java:71)
at com.binance.connector.futures.client.utils.ResponseHandler.handleResponse(ResponseHandler.java:35)
at com.binance.connector.futures.client.utils.RequestHandler.sendApiRequest(RequestHandler.java:56)
at com.binance.connector.futures.client.utils.RequestHandler.sendSignedRequest(RequestHandler.java:80)
at com.binance.connector.futures.client.impl.futures.Account.newOrder(Account.java:148)

There are several coins where I can not place the POST ONLY order from time to time.

May I ask you to check the BID/ASK price for SOLUSDT for the period 2025-04-21 10:10:15.473 -- 2025-04-21 10:10:15.531 , please?
I believe the bid/ask for SOLUSDT was 139.91/139.92
Confirm, please.
Regards,

Start with the issue's Binance Futures API request and exception log, especially the LIMIT order using timeInForce=GTX. Compare the reported SOLUSDT bid/ask and order timing for 2025-04-21 10:10:15.473–10:10:15.531, then determine whether the rejection is expected API behavior or a connector defect. Done means the cause is confirmed and any affected connector entry point is identified.

Written by the indexing model from the issue text.