I'm currently testing the MT4 bride and during a single Zorro session (i.e. no re-starts) everything runs fine after some minor adjustments to my script.
However, after re-starting both Zorro and MT4 during the weekend, Zorro wasn't able to close trades during market hours from the previous Zorro session.
I'm sure that multiple attempts were made, since I included a printf() function before exitLong() & exitShort().


A couple of points:

- I do receive a 'Error 013: Invalid expression ()' during the beginning of my script (only in TRADEMODE). I've read the manual about this error, but I can't pinpoint the exact cause.
- I also receive messages like '[EUR/USD::L00531] - not found (2123772 lots)' during the beginning. There's no error code included, so I'm not sure what's causing it, since there are no active positions in MT4 with this lot size.
- There's no 075 error message and there are no order-related error messages in the MT4 logs.
- No NFA flag is set.
- I don't run a hedge strategy, but I do run a multi-asset strategy where every asset is assigned to a single strategy.

The manual (MT4 bride) states: "Note that you can not run multiple strategies in parallel on no-hedging or FIFO compliant accounts.", but from what I understand this isn't the case in my setup (or IS it?).

There's also another issue. When I close Zorro during market hours to provoke / test this situation, all trades are automatically closed. How can this be prevented?



Edit: never mind, I saw there was a dialog box and I pressed too fast.

Invalid expression is a hard bug, a script crash due to a wrong expression.

Not found means the trade ending with 00531 was not found in your mt4 trade list and could therefore not be continued. This happens typically when you had closed it manually or when you continue a session with a different account.

Thank you for your explanation, Petra.

Now I see these 'not found' messages are explained in the manual, so I will make some notes!

As for this 013 error message, it isn't causing a crash in my script itself. As stated, it only happens in TRADEMODE during the beginning of a session, right after a data pre-fetch procedure in my script, that runs fine. There's no message in my .log file, but only in Zorro's output window:



Maybe this in an internal bug in the MT4 plug-in? I'm using version 4.24.

I will test this as well in a Windows environment. If I can reproduce this error with a sample script, then I can provide it to support when needed.

I notice that this 013 error doesn't occur in every session. Under Linux/Wine it often does, but not always. So far it doesn't under Windows 10, but that's only one single session so far. I will run more Windows sessions to find out more.

However, the main problem still remains. My script knows the positions, but it's unable to close open positions from a previous session.

I would fix the 013 bug first because such a bug can have all sorts of bad consequences. It's in your script. If it only happens sometimes then it's dependent on data content, prices or the like.

You can also in your screenshot see a date from 1899, so obvously something is wrong.

https://zorro-project.com/manual/en/trouble.htm

If you cannot find it, we have a script fixing service.

Good point, I missed that wrong date and this might cause this 013 bug.

I'm currently testing my script under Windows and the log shows a normal date range for the LookBack period in TRADEMODE without this 013 error, so the actual cause might be a wrong date handling issue by Wine. It's frustrating, because I prefer Linux over Windows as a future VPS environment.



I don't want to interrupt the live demo test during the week, but I will restart both Zorro and MT4 this weekend to see if it's able to close paper trades next week.

The reason is probably not Wine. There are still some subtle differences in some Windows date/time functions, but they should have normally no effect in the script.

A 1899 date corresponds to the number 0. So one of your functions under Linux returned 0 instead of a valid date. Maybe it's a missing timestamp in preloaded or downloaded history.

Luckily, you're correct JCL.

This 013 error only occurs on specific dates and only in TRADEMODE with StartDate = NOW. From what I've seen, it only happens during the end of a weekend or right after it. Maybe setting a BarMode can solve this issue? I can't test this right now because there's currenly no 013 error / date 0 issue.

I don't believe it's the cause of my main problem. Even without this error I'm not able to close trades from a previous Zorro/MT4 session.

My trading script does return messages like these during the beginning and there is a recent *.trd file in my Data folder, but active trades remain open after exitLong() / exitShort() attempts.

I've made a sample script which uses a duplicated *_d.trd version from my trade script to view all active trades.
Just like my trading script, this sample script is unable to close the trades from my previous MT4 session.
There are no error messages at all in the MT4 & Zorro log files. In fact there is no sign from any trading attempts.

output:


code: