I'm running WL Pro 5.3.44.0 under Vista. If my DSL should experience even a brief outage AND THEN THE CONNECTION IS FULLY RESTORED(even if the outage was 1 minute or less) and I have streaming strategy windows actively running, then the program is simply unable to reconnect properly. Often the program just fails to stream properly and locks up totally if I try to de-select streaming and re-select it again. (and going into task-manager and forcing WL to shut down might not get it working again a 2nd time it is run).

Sometimes the connection indicator on the status bar becomes red (with no way to revive it, even by clicking on it, and the program already thinks it is logged in to fidelity).

Sometimes the connection indicator is green but it simply does not behave as if it were conected and there is no way to revive the connection.

EDIT: Somtimes the connection indicator flashes from gree to red and behaves as if it were disconnected with no way to revive the connection.

I repeat: the problem is that DSL was interrupted and then fully restored but WL fails to properly reconnect.

The key point here: Other programs, like Active Trader Pro, and ThinkorSwim Desktop HAVE ABSOLUTELY NO TROUBLE RECONNECTING if there is a brief DSL disruption. ZERO, NADA, ZILCH...no problems at all. They all reconnect just fine automatically. Only WL pro has problems getting reconnected or locking up if there is even the briefest DSL outage. There is no way to reconnect either automatically or manually. If I am LUCKY the program won't lockup and then I'll get to quit and restart it, but often I'm not that lucky. This is a major problem that should be fixed. WL Pro SHOULD be able to reconnect if DSL has a brief outage, but my experience is that it utterly fails to do so even though other trading platforms have ZERO problems reconnecting.

Please address this issue.

Thanks,

J.

Describe your Workspace environment(s). Most specifically, I'm interested in the number of streaming windows, their symbols, and their data loading control settings.

My workspace environment is 4 streaming windows. .SPX, RUT, EMM & IYR. The date range is 15 months for all 4 symbols. The time scale for SPX and EMM are 60 minutes. The time scale for IYR is 30 minutes. The time scale of RUT during today's lockup was set at 60 minutes. Typically I do set RUT to a 1 minute time scal after the 1st trading hour, but I left it set to 60 today and the lockup still occurred.

Thanks,

J.

There's nothing too demanding there, so please create a ticket with a reference to this topic so that we have it in our queue. Although I have to force disconnects, reconnecting always has worked fine in my testing (and I assume Fidelity QA too). While reconnect logic wasn't targeted specifically for 5.4, other changes affecting error handling could potentially help, so hopefully you have a better experience when 5.4 becomes available (probably next month).

I'm running into this same problem with reconnect not reconnecting manually or automatically. I have not had the app crash, but restarting the app when I have three main workspace windows open (that I'm still having to change the scale for each saved strategy) makes it a real pain. Was there a fix to the reconnect issue?

QUOTE:
Was there a fix to the reconnect issue?

I don't remember one that specifically targeted that (which doesn't mean there wasn't), but a lot has changed in the last 6 years. Either way, it sounds like you're reporting that there's a problem with reconnections - at least intermittently.

Yes. I had problems yesterday and the day before 12/9 & 12/8. More so yesterday. After reading this post I stopped running all the scripts at the same time, which I've been doing for months without issue. Also, rebooted yesterday. Today I've been on another project and can't say if it is still happening.

Yesterday, clicking on the red "Disconnect" at the bottom didn't seem to do anything. Only restarting the app would reconnect me. You answered my original question regarding a specific fix and yes, this is an old post, but the only one addressing the issues I was seeing.

If you have any tips on reconnecting without restarting the app, that would be great. If the problem returns, I guess I'll open a ticket then.

QUOTE:
If you have any tips on reconnecting without restarting the app, that would be great.

From a logical standpoint, changing to some other streaming provider (e.g. Yahoo) in Preferences, using it briefly, and then going back to Fidelity may help.

Thanks, I'll give that a try next time.

I have had that problem like.... forever. However ever since I downloaded 6.9.15 it seems that the application is now able to handle internet interruptions much better. I have had 6.9.15 for a few days now, and I have experienced 2 brief interruptions and 1 long one.

On older versions the only choice was to quit the application, restart it and go through the pain of setting up everything again. In the last couple of versions, the workaround of logging off and relogging on (without a restart) seemed to work most of the time. But in this new version I have seen that it has handled the interruptions much more gracefully, automatically restarting the streaming mode without me having to do anything (at least during the brief ones). The long one did require a restart... but it was a complete breakdown that lasted for about 20 minutes and I was trading from a site without a backup internet service (as dumb as that is).

This means that under usual circumstances (with a backup internet available) the application will behave itself as the other trading apps, being able to handle brief interruptions.

Will continue to observe this behavior, but if anything... good job guys.