-
Notifications
You must be signed in to change notification settings - Fork 537
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NFIX2: bingx: Could not fetch historical candle (OHLCV) data #333
Comments
did you try with other standart strategies ? |
FT v2023.09 In addition to NFIV7 and NFING, I have tested some other strategies with bingx exchange and I don't have error 100204 in any of them and the trade is completed. I am not sure if these strategies are standard, but they work without error 100204. |
It is possible that they don't have BTC/USDT pair ? |
They have BTC/USDT. I still can't find where the problem is. But for now I use an alternative solution using Message WebSocket. I intercept the signals for kucoin and deliver them to bingx, and the trades are done successfully in bingx. |
This error is normally generated when an exchange doesn't have enough volume or doesn't provide more candles than said amount. You can read the following issue which has the same problem on the same exchange, freqtrade/freqtrade#9074 (comment) |
Hi,
When I used the NFIX2(v12.0.640) or NFIX4(v14.0.339) on bingx exchange, the bot stopped with the following warning:
2023-10-21 23:46:24 - freqtrade.exchange.common - WARNING - _async_get_candle_history() returned exception: "Could not fetch historical candle (OHLCV) data for pair BTC/USDT due to ExchangeError. Message: bingx {"code ":100204,"msg":"","timestamp":1697946384613}". Giving up.
This is not just for BTC/USDT, warning happens for all pairs in pairlists.
Exchange error 100204 refers to no data.
While other strategies do not have this error on bingx and work correctly. For example, NFIV7 and NFING work.
The text was updated successfully, but these errors were encountered: