@jcl: Would appreciate your thoughts before I try using the post-surgery trd. 116k went to 12k. Is this expected? 90% of a trd is the algovars?

Thanks.

I estimate for algovars a size of about 1 kb multiplied with the numbers of algos and assets.

Thanks @jcl. That puts the size reduction is in the same ballpark, so I'll give the tiny trd a try.

FYI, I save a copy of the trd file most every weekend. I tested starting Zorro (in a test environment, not live) with these backups, and had to go back a number of weeks to find an un-corrupted trd. Zorro ran continuously over that period, and the weekly trd files have different sizes. Since Zorro was never stopped and restarted, the trd file was apparently never read - only written to. Unfortunately, especially given the passage of time, I have no hope of correlating the corruption to anything else. But from these circumstances a reasonable suspicion could be a rare pointer/buffer problem in Zorro?

HTH.

@jcl: The saga continues. The tiny trd allowed Z12 to start. But:

a) Intermingled with the "resumed" messages were a number of "closed" messages. The "closed" messages were all for real trades, and all exactly 1 lot. Is this expected?

b) After the "resumed" messages came a slew of Trails, Stops, and Longs. I assume this is normal as Z12 adjusts to the new market conditions it finds? (Although without the benefit of the missing AlgoVars...)

c) Lastly, the net result of the above seems to be that the account balance being reported by Zorro is accurate, the number of open trades matches the number of open positions in the broker's web interface, but Zorro's view of the value of these open positions, including which are winning vs. losing, is incorrect. Is anything to be done?

FYI, the trd file has grown from 12k to 57k.

Thanks.

Closed means that the trade was not open anymore. You probably closed it?

Open value includes swaps and commissions, so it can differ.

Thanks @Petra.

- No, I didn't close anything. Wanted to keep everything unchanged on the hope the trd could be fixed. Also very suspicious that in every case exactly 1 lot was closed - no trades of 1 lot were ever opened.

- Open value is ~1/2 what the broker shows, even though balance is the same. Swap & commission could account for that?

There can be 1000 reasons of differences, hard to tell with so vague information. Compare the different trade in the platform trade list with the same trade on the trade status page. There you can see all parameters of the trade and calculate the open value yourself.

Thanks @Petra. Yes, I am aware of that process, and a full investigation would also include the trades done when Zorro "reconciled" to the new world it found after being disconnected for many days...

Before embarking on that, I was hoping @jcl or someone who knows the internals of Zorro and trd processing could add insight into why _exactly_ 1 lot closes during resume, and why the open value might have gone off (while balance is correct).

Hmm, how am I supposed to know your trade sizes and open values? If you want, you can get a support ticket and send them the log, trd file, and trade status page. They will look through all and explain the open value and why 1 lot was closed. I don't think Zorro internals are needed.

Thanks @jcl. Clearly you are not supposed to know what you can't. The question was explicitly if what you DO know (Zorro internals) could shed some light as to why on restart with AlgoVars removed:

- Zorro would at startup time of trades resume enter only multiple close orders across all Assets of exactly 1 lot - is 1 lot some sort of default or fall-back?

- Zorro would "lose its mind" and not know the correct values of open trades, while reporting correct account balance.

Thanks.