Price Filter tickSize problem on creating an order

[caebwallace]

Version

v0.0.76 (9119c6d)

Description

As the ticksize in 0.1 and the create order use 2 decimals, there is a 'PRICE_FILTER' error.
https://api.binance.com/api/v3/exchangeInfo?symbol=AAVEUSDT

AAVEUSDT Buy Action Grid Trade #1 (12:10:50.056): STOP_LOSS_LIMIT
- Order Params: 
{
  "orderParams": {
    "symbol": "AAVEUSDT",
    "side": "buy",
    "type": "STOP_LOSS_LIMIT",
    "quantity": 1.3895,
    "stopPrice": 359.14,
    "price": 359.49,
    "timeInForce": "GTC"
  }
}

Execution failed (12:10:50.789)
Job: Trailing Trade
Code: -1013
Message:
Filter failure: PRICE_FILTER
- Current API Usage: 366

To Reproduce

Place a manual limit BUY order to AAVEUSDT with a 2 decimals price.

[habibalkhabbaz]

Hello @caebwallace
This is happening because the tick size got updated by Binance and not updated in the bot.

Temporarily fix:
Go to Global Settings and just click Save Changes then Apply to global only.
This will refresh exchange info for all symbols.

[caebwallace]

No effect, continues to display 2 decimals on AAVE after applying Apply to global only
And manual BUY order has the issue (even bot trigger as AAVEUSDT is dropping now ^^)

[chrisleekr]

I had the same issue last night.

The issue was as @habibalkhabbaz mentioned.
But that was not fixing all issues.

A quick fix is to remove the symbol information when saving Global Settings.
This will be released as v0.0.77.

A proper fix will be periodically refreshing the exchange/symbol information. I will add the proper fix later.

Updated:

Docker image has been released.

Restart with a new image

docker-compose -f docker-compose.server.yml pull
docker-compose -f docker-compose.server.yml up -d

And then Go to Global Settings and just click Save Changes then Apply to global only.

Let me know how it goes, and close the issue if it's resolved.

[habibalkhabbaz]

Thank you @chrisleekr for the quick fix 💪
I think the proper fix would be changing the permanent Redis cache to TTL Redis cache for 12 hours in getSymbolInfo (12 hours is enough for caching symbol info)
So that, when a symbol is trying to retrieve its info from getSymbolInfo and the TTL is expired, it will retrieve the new info from API.

[chrisleekr]

@habibalkhabbaz Yeah, I agree. Unfortunately, I am using HSET to save the symbol info which is not possible to set EXPIRE.
So I will figure out a different way.

[chrisleekr]

I assume the issue is resolved. I will close the issue.

[caebwallace]

Yep, will test that this afternoon !

[caebwallace]

To confirm you that v0.0.77 fix that issue on Apply to global only
=> perhaps we could add a cronjob that runs every 6 hours (or better every hour), cleans redis trailing-trade-symbols.symbol-info and refresh exchangeInfos for all selected symbols ?