Upgrade to 6.9.21.15 went well.

I run execution on an Amazon AWS instance. Trades early in the day went fine.

However later trades started failing with the following error:

"The remote server returned an error: (500) Internal Server Error."

Closing down WealthLab, and then restarting it, and then placing a trade addressed the issue.

I assume at some point my login status changed. Perhaps there was a network interruption, but this was running on Amazon AWS, and I monitor for network issues, and in this case I was not aware of any issue. Perhaps an interruption occurred within Fidelity.

Is there any way of getting the current login status?

I see that I could potentially identify that a trade failed by parsing the Orders XML file, which I do already for other reasons, but is there a better way to detect this kind of trade error?

Thanks
Phil

I guess it's expected:

Orders Tool
Wealth-Lab Pro will now handle the intermittent server error that can result in the stale "Submitted" order status condition. If the error is detected, the order should fail with an "Error" status.

Wealth-Lab Pro® 6.9.21

@psimmons - Thanks for the report! We're still trying to discover why this intermittent, elusive server condition occurs. At least now, there's no doubt that an error occurred with the order and that you need to take the action that you did. We'll keep trying to resolve this once and for all.

Happened with me too. The upgrade broke WL and my autotrading won't work due to the server error. And now if I'm on a plane I can't work on strategies since it requires a login. Is it possible to go back to the old version? Thanks

You will find your question answered by the link in my post #2 above.

QUOTE:
The upgrade broke WL and my autotrading won't work due to the server error.

Yes, this update broke my semi-autotrading system too. Before the update, my login script worked flawlessly without any issue in the past 5+ years. With this update, although I'm still working on it but so far my login script is failing intermittently. Because the new login prompt is so unfriendly with the script, it's very difficult to workaround all the possible issue.

QUOTE:
I can't work on strategies since it requires a login.

Yes, this is a huge drawback in this new update. You no longer be able to work on your strategy code without internet access.

QUOTE:
Is it possible to go back to the old version?

I'm sticking to 6.9.20 for the time being and maybe extended period of time until I find all solutions. So far this 6.9.21 is worst ever WLP release to me.

Thank God that option to go back worked and the server error stopped and the annoying extra forced log in stopped. Thanks!

Please don't deprecate that version since this was the last time I'll ever upgrade WL since the new version issues are significant.

Just upgraded yesterday.

I received the "Internal Server" error yesterday for most of my orders and today for all my orders. Nothing ran at all today.

So far this has cost me $2400 in missed gains with my autotrading.

There was a ugly snafu on the last upgrade, as well. Might I suggest that you Fidelity folks test your code before you release it for use by the public? Especially considering this update appears to crash abruptly on a known problem that has not been resolved for years. This disaster should have been prevented.

Perhaps it would be appropriate to change the name of the product from Wealth Lab Pro to Wealth Lab Amateur Hour.

@Nikko

Is the "Internal Error 500" occurring shortly after WLP is started or after a prolonged period of use?

Yesterday WLP placed five trade entries in the first 20 minutes and then stopped working. It should have entered 10 trades and closed all at the end of the day.

Today it should have place 8 trade entries by now. It did not.

WLP is restarted every morning 1 hour before the opening bell. Data files are updated after the close and again prior to the open.

Today WLP placed 6 trades thru 9:50 ET. Then stopped accepting orders and returned 500 Internal Server Error thereafter.

Did WLP start returning error 500 right after 9:50 am ET (i.e. in the first 20 minutes) or maybe at a later time?

Or to put the other way round: have you seen any successful trades say after 10:30 am ET?

Thanks.

All trades were placed by WLP at 9:50:03 ET or prior. No orders are being accepted after 9:50:03 ET. Unsuccessful attempts are being made every 10 minutes.

Thanks. I'll pass it on to the development team.

Do you restart WLP during the market session when you get Error 500?

No. This is live intraday trading. Exit orders and EOD orders would be lost on a restart.

Could you please give it a try? We wonder if this makes a difference.

Restarted. Retained order and alert lists. Seems to be monitoring positions. Next orders are due for end of day to flatten all outstanding positions. I will let you know what it does.

After restart, WLP was able to detect when an order was about to be sent that duplicated a order that I had already placed by hand, and correctly gave the message "Due to an existing, conflicting order ..." However, it did not flatten any positions at End Of Day. All generated the 500 Internal Server Error at End Of Day and needed to be flattened by hand.

Thank you for the feedback. I'll keep you in the loop for updates later this week.

Today, WLP placed 1 trade at 9:45 ET, then issued Internal Server Errors for the next 2 trades. I quickly restarted WLP and it resumed placing 4 more trades and correctly generated the corresponding 4 exit limit orders. At some point in the morning it logged me out, though there is no evidence of an internet connection interruption in the logs of other trading programs running at the same time. I logged back in, but WLP never placed any more trades or sent any more orders.

Today, WLP again logged me out and locked up. Had to restart.

Most trades placed, except one order that returned an error "the operation has timed out".

The key developer has some ideas that he'll be trying out this week with regard to Error 500 and delayed data. I'll get back to you as soon as I have an update.

Sorry for the inconvenience.

WLP still logs me off 5-6 times per day during market hours. It also still throws the Internal Server Error 500. Any word on the developers' progress fixing these problems?

Agreed, .21 is pretty poor user experience. There's progress with build 22 lately as developer thinks the delayed history and possibly the forced login issues may have been solved. I think it requires more testing which continues next week.

Nikko, going back to the old, stable version, worked for me. It's in the Users\name\AppData\Local\Downloaded Installations\guid directory.

That works because you did a fresh install 6.9.20. New installs are saved in that folder, not upgrades. And some previous versions (6.9.19) will get stuck in Nasdaq agreement loop.

Just want to add here that the "Server 500 Error" is the "Stuck Submitted" problem we've had for a long time. This build handles that error so that the order doesn't go "stuck" and shows you that it fails immediately. That said, there's a good chance that some order change exacerbated the frequency of the problem, and we're closing in on it now.