Hi guys,

I need help with my Yahoo data (I have the extension 202O.02.23 instaled).
I would like to know why symbols that ends with 11 like BPAC11.SA or TAEE11.SA, they are not localized by Yahoo Finance and it not updated this database? The bug is descriptioned like not localized.

I hope to hear you from soon.

Aloysio

Hi Aloysio,

Works for me:

[4] BPAC11.SA 755 bars 11.03.2020 755 bars added

Here's a rule of thumb: please retry until it works for you. Looks like a temporary glitch of the free data feed. It happens.

Hi Eugene
It still not working... some bars appeared but wrong...

Right click on the instrument's chart and choose "Reload chart history".

Eugene,
Perfect, well done!
Thank you

Glad to help you.

Hello


i am getting also an 404 update. I checked the ticker and I also performed a "Reload chart history". The Chart still stays empty

i.e
[8] UNA.AS Error: The remote server has returned an error: (404) Not found.
[0] UNH Error: The remote server has returned an error: (404) Not found.

The Tickers areavailable
https://finance.yahoo.com/quote/UNA.AS/
https://finance.yahoo.com/quote/UNH/

I have the feeling the more tickes I am updating the percentage of 404 error messages is increasing.

Do you have any idea?

Thank you

Andi

Hello,

Predictably, both symbols work for me:

Updating DataSet test ...
Preparing requests ...
Requests are ready to go.
Yahoo session cookie cached
Updating Security Names for 2 symbols...
Security Names updated.
[1] UNH 8968 bars 15.05.2020 0 bars added
[0] UNA.AS 5571 bars 15.05.2020 5571 bars added
Update completed (3.490 sec)
----------------

But you may be onto something with your guess about the number of symbols being updated. Keep in mind that Yahoo is a free service and automated downloaders generally aren't welcome. Here are a few things to try:

1. Reduce the number of tickers in your DataSets.
2. Try to update them DataSet by DataSet. Make a pause.
3. Another possibility could be that you're hitting a 'bad' server so the glitch is temporary as said in post #3.

Good luck!

Hello Eugene,

thank you for the replay.

I reduced the numer of tickers in a dataset and it now it seems that it works a little bit better.

Have a nice day!

Good news to hear!

This workaround doesn't seem to work anymore. I remember Eugene once told me the number of max symbols I can have in a dataSet. What is it again ? I split my 8000 symbols into 3 and I checked the log, it still says something
(I am using yahoo data provider)
NFLX Error: The remote server returned an error: (404) Not Found.

You get what you paid for with free data providers. Yahoo is a free data provider that comes without any warranty or promises. You're already pushing any meaningful limits by updating huge DataSets. If you need guarantee and support, subscribe to IQFeed or use Fidelity data.

I have reduced my set to 2000 symbols but it is just hanging there. Perhaps the yahoo session cookie is outdated or like you said the server failed... Let me wait a bit and see.

Restarting WLP to reset the Yahoo session cookie is a good idea. Also you might want to change IP address somehow (different ISP or a VPN). But reducing the DataSet further down to hundreds rather than thousands and making a pause between data backfill seems the most promising. or simply retry at a different time.

I see, I have been on the same vpn connection for a week. Let me get out of it and try it tomorrow without/with vpn to see which one works. Fidelity data seems to be working. Good enough for now

Thank you for that, Eugene.

It's 6:15 PM ET, more than 2 hours after the close. Finance.yahoo.com has updated data. When I try to update manually I get the errors below. These are all valid ticker symbols.



[5] WFC 12150 bars 8/4/2020 0 bars added
[2] WLTW Error: The remote server returned an error: (404) Not Found.
[3] WM Error: The remote server returned an error: (404) Not Found.
[0] WBA 10184 bars 8/4/2020 0 bars added
[7] WELL Error: The remote server returned an error: (404) Not Found.
[9] WRB Error: The remote server returned an error: (404) Not Found.
[1] WMT 12090 bars 8/4/2020 0 bars added
[0] WYNN Error: The remote server returned an error: (404) Not Found.
[2] WU Error: The remote server returned an error: (404) Not Found.
[4] WHR 11970 bars 8/4/2020 0 bars added
[6] WRK 1288 bars 8/4/2020 0 bars added

Since changes last year - about the time that Europe implemented GDPR - requesting Yahoo! data can be hit and miss. In a few hours, it's likely to return all symbols - you just never know. For reliable EOD data with loads of other features we highly recommend a subscription to Norgate Data (see the announcement on Wealth-Lab's What's New home page).

@MrIzzy, try several times until it works. If it doesn't, retry next morning. If you search the forum for Yahoo 422, 404 errors you'll discover more suggestions/