For some strange reason, Fidelity Static data stopped updating yesterday. Whenever I try to refresh data now, it returns really fast with a message like this:
Updating Provider Fidelity Investments ...
Updating 1 Minute data ...
Provider update complete for Fidelity Investments
----------------
Update completed (2.614 sec)
----------------
It returns too fast (I have thousands of tickers, and even checks were much longer earlier) and does not attempt to update Daily data either.
I am wondering if some of the configuration files got damaged.
Thanks,
Maxim
Size:
Color:
Possible reason: either one or more .WL files that make the 1-min data folder got corrupt or there was a reverse split that affects one of your 1-min symbols due to a live bug which breaks data update. In both cases, resolution is the same:
1. Enable
hidden file visibility2. Delete this folder:
C:/Users/Windows user name/AppData/Roaming/Fidelity Investments/WealthLabPro/Data/FidelityStaticProvider/1 Minute3. Update data and wait until your historical 1-minute data is backfilled from scratch
Although it's possible, I won't recommend to figure out which one of them had a reverse split since you have thousands of tickers. But if you were lucky you probably could delete just that symbol (or symbols).
Some background:
1. Corrupt data:
Fidelity data 0 bars when updating SPY 1 minute DataSet2. The bug:
WL will only update 1 minute Fidelity data. Long story short:
Open Issues >
Fidelity data can not be updated except for X minute
Size:
Color:
Eugene, thank you for your recommendations. I was able to use "divide&conquer" approach to move specific subfolders under FidelityStaticProvider/1 Minute folder to some other backup folder to find a specific letter folder which was causing a problem and then do the same approach within this problematic folder to find a single file that was causing this issue. In the end, I had to quarantine a single ticker to get the system back to working state.
Would uploading the problematic help you in any way to troubleshoot this issue further or should I just delete it?
Thanks,
Maxim
Size:
Color:
Maxim, glad to have helped.
QUOTE:
Would uploading the problematic help you in any way to troubleshoot this issue further or should I just delete it?
It's up to you. It won't hurt to have the problematic file as an evidence
if Fidelity considers fixing this bug at some future date. If the zipped file (.WL isn't allowed, .ZIP is) is under 3MB in size please attach it when replying. If it's bigger then simply delete it.
Size:
Color:
File attached. While looking at it in HEX viewer, I think that it has header area damaged/overwritten with some Fundamental data.
Size:
Color:
Thanks.
Size:
Color:
Size:
Color: