Closed ozitrance closed 3 years ago
Seems like it's something similar to this: [](https://github.com/freqtrade/freqtrade/pull/3086
FTX returns a string, something like "Order cancelled", after cancelling the stoploss order and I guess freqtrade is expecting a dictionary...?
the latest develop (just pushed) will fix this for future canceled orders
I do suspect that you will have to remove this order from the database manually to get to a "clean" state again.
Sorry for the inconvenience
I just tried now with a new database and it seems to be working fine and as expected, updating the stoploss orders without crashing or anything
Thank you very much!
FIrst of all just wanted to thank you all for this amazing tool and this amazing hard work :1st_place_medal: Thank you!
Describe your environment
Note: All issues other than enhancement requests will be closed without further comment if the above template is deleted or not filled out.
Describe the problem:
Freqtrade crashes when using FTX.US. Seems like it's related to the stop loss order? OR entering/pulling data from the database?
Steps to reproduce:
Configuring ftx.us as the exchange in the config file (as instructed in ):
Running the bot. Seems like it's cancelling the stop-loss order trying to create a new one and then crashes. I think it's related to the database? I saw a lot of these rows when running on dry-run but I though it's only because it is dry run. And it never crashed on dry-run either.:
Observed Results:
Relevant code exceptions or logs
Note: Please copy/paste text of the messages, no screenshots of logs please.