Bug#2:
The manual states:

for(last_trades)
Quote
A for loop that cycles backwards through open, pending, and closed trades with the current asset and algo, starting with the last trade

The provided log shows that it delivers not only "open, pending and closed" trades but also some missed, 'invalid' trades (that are neither) - which - as YOU WROTE - Zorro is not even supposed to store!

Right now, to achieve their stated objective, does one have to write

for(last_trades)
if (TradeIsPending or TradeIsOpen or TradeIsClosed)
.....
???

The same issue is with for(all_trades) and for(past_trades).

I do not believe you meant (and there is any valid purpose) delivering such 'invalid' trades with these macros.

So, let's just make them actually do what they are supposed to.


This is a bug and it is in v 2.30.