Closed medenlin closed 2 years ago
Thanks for the detailed description / bugreport. I've been aware of "Odd" behaviour in this area - but was unable to recreate the problem / know the exact events (@eSeR1805 this is the problem i was trying to trace down in #6861 but was unable to...).
However with this description, i was immediately able to recreate this.
I think i have a fix for this (at least in mind) - but will obviously need to test that a bit further before releasing that - to avoid unintended sideeffects.
Is there any workaround for this issue until the update is released?
Sure, you can either avoid using multiple orders, or make sure that the adjusted order does not time out.
It's fixed in the latest develop - let me know if you still encounter this after updating to that.
It's fixed in the latest develop - let me know if you still encounter this after updating to that.
Ok. I update to latest dev version and keep observing :)
Confirm! Canceling adjustment orders by timeout works correct now. Thank you!
Describe your environment
python -V
)pip freeze | grep ccxt
)freqtrade -V
ordocker-compose run --rm freqtrade -V
for Freqtrade running in docker)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:
When Position adjust triggered and order timed out, then Freqtrade fully remove it from database. See log with my comments.
Steps to reproduce:
Observed Results:
What happened? The position will be instantly deleted from the database, disappear from the list and no longer served by Freqtrade.
What did you expect to happen? Cancel only last adjustment order
Relevant code exceptions or logs
Note: Please copy/paste text of the messages, no screenshots of logs please.