As a WealthSignals subscriber, I wanted to learn how to use the Trader which I read is supposed to work in latest WLP version. No luck ... I can't get past "LOG IN TO WEALTHSIGNALS".

Verified my credentials were correct by going to WealhSignals.com, logging out, then loggin in. Worked perfect.

Any suggestions?

Like I told you in our conversation on WealthSignals site (Connect to Wealth-Lab with WealthSignals Trader Tool), the WealthSignals Trader tool stopped working with the launch of WealthSignals 2.0 last winter. Recently released WLP version 6.9.20 fixes it (but not for WLD users yet):

Wealth-Lab Pro 6.9.20 brings WealthSignals Trader back!
Download and execute signals by SuperBands in WLP's Quote Manager

To learn the WS Trader tool, check out the Wealth-Lab User Guide. To make it work first you have to upgrade WLP to 6.9.20. However, note that there are known issues in this update:

WLP 6.9.20.7 (07/10/2019) Update

We recommend to:
1. Uninstall Wealth-Lab Pro, and,
2. Re-install the latest version 6.9.20 from https://www.fidelity.com/wlp

Not sure why you thought I was downlevel. I had upgraded to 6.9.20. In fact, I was/am at 6.9.20.7. I did the uninstall/reinstall. & everything was working fine. As I said in my original message, I did this to try the WealhSignals.Trading Tool. However, when I tried to Login to the Toool, it failed.

Today, I changed my passwords to make WealthLab & WealthSignals the same. I then tried the WealhSignals.Trading Tool again ... and log in worked. So, right now, all it good.

BTW, I had read the documentation you reference, but they don't help when you can't login!

I never intended to think that you or somebody else were "down level". There are so many support cases recently so I decided to provide as much information as possible to stay on the safe side. You never know given the frustration that the new 6.9.20 build has caused to the users.

Apparently there was a problem with your password or you were entering the username without checking for case sensitivity? Glad you resolved the issue on your own.