mirror of
https://github.com/freqtrade/freqtrade.git
synced 2026-01-29 10:20:25 +00:00
Deployed 711e680 to develop in en with MkDocs 1.6.1 and mike 2.1.3
This commit is contained in:
File diff suppressed because one or more lines are too long
@@ -3095,7 +3095,8 @@ This also means that the first call will be at the start of the next candle afte
|
||||
Returning any other price will cancel the existing order, and replace it with a new order.</p>
|
||||
<p>The trade open-date (<code>trade.open_date_utc</code>) will remain at the time of the very first order placed.
|
||||
Please make sure to be aware of this - and eventually adjust your logic in other callbacks to account for this, and use the date of the first filled order instead.</p>
|
||||
<p>If the cancellation of the original order fails, then the order will not be replaced - though the order will most likely have been canceled on exchange. Having this happen on initial entries will result in the deletion of the order, while on position adjustment orders, it'll result in the trade size remaining as is.</p>
|
||||
<p>If the cancellation of the original order fails, then the order will not be replaced - though the order will most likely have been canceled on exchange. Having this happen on initial entries will result in the deletion of the order, while on position adjustment orders, it'll result in the trade size remaining as is.<br />
|
||||
If the order has been partially filled, the order will not be replaced. You can however use <a href="#adjust-trade-position"><code>adjust_trade_position()</code></a> to adjust the trade size to the full, expected position size, should this be necessary / desired.</p>
|
||||
<div class="admonition warning">
|
||||
<p class="admonition-title">Regular timeout</p>
|
||||
<p>Entry <code>unfilledtimeout</code> mechanism (as well as <code>check_entry_timeout()</code>) takes precedence over this.
|
||||
|
||||
Reference in New Issue
Block a user