Yahoo errors 422 (unprocessable entity), 404 (not found)
Author: jpolito1
Creation Date: 7/22/2020 10:27 PM
profile picture

jpolito1

#1
I will soon transition from Fidelity Wealth Lab Pro to Wealth Lab Developer. I have the Yahoo! Finance extension installed on Wealth Lab Pro. I have been informed that I can use it in Wealth Lab Developer, so to test it I duplicated an existing Data Set and designated Yahoo Finance as the provider. When I update the data, Yahoo finds most symbols but it will not recognize others. When I enter the symbols in the Yahoo Finance website, it finds all of the symbols (that I have tried). Here is an excerpt from the update log from Wealth Lab Pro.

[4] FSDAX 9126 bars 7/21/2020 9126 bars added
[2] FSDCX 7573 bars 7/21/2020 7573 bars added
[9] FSHBX Error: The remote server returned an error: (404) Not Found.
[1] FSEAX 6865 bars 7/21/2020 6865 bars added
[3] FSDPX 8522 bars 7/21/2020 8522 bars added
[0] FSHCX Error: The remote server returned an error: (422) Unprocessable Entity.
[8] FSELX 8817 bars 7/21/2020 8817 bars added
[8] FSMVX Error: The remote server returned an error: (404) Not Found.
[1] FSLVX Error: The remote server returned an error: (404) Not Found.
[7] FSENX 9840 bars 7/21/2020 9840 bars added

The same thing occurred with some indexes:

[5] ^IXUT Error: The remote server returned an error: (422) Unprocessable Entity.
[1] ^IXBK Error: The remote server returned an error: (422) Unprocessable Entity.
[3] ^IXIS Error: The remote server returned an error: (422) Unprocessable Entity.
[4] ^IXK Error: The remote server returned an error: (422) Unprocessable Entity.
[5] ^SPX Error: The remote server returned an error: (422) Unprocessable Entity.

Can anyone tell me why this is happening and how I can fix it?

Thanks

profile picture

Eugene

#2
Please search the forum before raising an issue. Thank you. Both have been discussed and explained:

Yahoo provider Error 404 on symbol
Yahoo provider Error 422 Unprocessable Entity

Summary:

1. It's not data provider's fault.
2. Code 422 is temporary, and some symbols may just not exist with the free data provider (404).
3. Retry later.
profile picture

kazuna

#3
Apparently Yahoo! Data Provider doesn't support the symbols I trade.

QUOTE:
[1] GDXJ Error: The remote server returned an error: (404) Not Found.
[6] XLE Error: The remote server returned an error: (422) Unprocessable Entity.
[2] IBB Error: The remote server returned an error: (422) Unprocessable Entity.
profile picture

Cone

#4
Y! does support them, but mileage varies. These symbols work for me (hitting European servers). Try restarting to refresh the Yahoo! cookie (not sure if clearing IE browser cache too will help).

Note that Y! is generally fine for a free source to get started, but you shouldn't rely on it for trading. At least once or twice a year you can expect an outage for several days during which we have to respond to site changes or other obstacles for downloading data.
profile picture

Eugene

#5
@kazuna

It looked like off topic in the topic where you posted this. I've moved our replies to a suitable thread like this one.
profile picture

thodder

#6
I'm running into similar errors with Yahoo. I was hoping to be able to use free sources of data with WLD (now that Fidelity is decommissioning WLP). Which providers are better?? I only need EOD so I thought the free sources would be fine.
profile picture

Eugene

#7
Let's please not turn this very specific thread into yet another "looking for provider alternatives" topic. If you're running into errors 404 and 422, can we have a summary to work with:

1. what symbols (you may attach the data update log)
2. at what time of day
3. how many symbols in the DataSet
4. have you restarted WLD prior to the morning (i.e. is Yahoo's saved cookie from yesterday or is it fresh)
5. anything else you can think of

Thanks.
profile picture

thodder

#8
Mainly I'm posing the question as there are probably other Fidelity users who are migrating to WLD. That means we are experiencing moving from Fidelity data to another provider for the first time. I had some Yahoo datasets in WLP, but now my Fidelity datasets are Yahoo ones creating more symbols to update.

#1 I can create a support ticket for that if we need to go that route.
#2 I usually start my computer and WLD around 7am EST and update all data
#3 This morning the log entry stated "Updating Security Names for 1273 symbols..." for updating Yahoo data.
#4 Yes, computer and WLD restarted
#5 My datasets contain stocks, ETFs, mutual funds plus the indices dataset installed with WLD.

I assume it is volume related as Yahoo provider starts out fine, but after a while I start getting 404 and 422 errors more frequently. Some 404 might be valid as I need to clean out obsolete symbols. Fidelity had a Fidelity Data tab in Data Manager which helped rename and remove symbols that got errors. I'm not sure if there's a tool to help with that in WLD.
profile picture

Eugene

#9
IMHO using like 1K symbols is pushing the limits of the free feed. Like suggested in other topics for the similar issue, a) break your DataSets into smaller ones; b) update them by one with a delay; c) reduce the number of symbols; d) retry later.
profile picture

thodder

#10
I definitely understand. I figured the number of symbols was part of the problem.

One reason I do "Update all data..." is to take advantage of the option "Delete data for Symbols that are not contained in Datasets" to clean up extra data that is no longer needed.

I'm following most of your advice except (b). I'm in the process of reducing datasets and checking datasets for obsolete symbols. I tend to update an individual dataset before running a strategy against it just to make sure it's up to date.
profile picture

superticker

#11
QUOTE:
2. Code 422 is temporary,...
That appears to be true. If I try to ...

1) reload the chart history and get "No Data"
2) then I push the "Update data for all selected providers" button on Data Manager.

I get the 422 error in the download logs.

3) Then if I wait an hour and try again, it works as expected.

So it's a throttling method on the Yahoo server side that's outside our control. I would avoid doing a "reload chart history" operation to avoid this error if you accessed the ticker symbol in question recently with Yahoo.
This website uses cookies to improve your experience. We'll assume you're ok with that, but you can opt-out if you wish (Read more).