No changes were made and y’day it was all loading/working fine until night around 10PM when I refreshed the page and started seeing the below.
Hey @Chintal_Patel , this error is caused by a symbol being removed by the data provider. According to the logs it is SICP.US
which was available on OTC market and seems to be renamed to SICPQ.US
which is available.
Just find this asset, edit it, open the prices tab and change the price data source to SICPQ (should be on the list - if not, you can search for it).
On my side, I’ll make this error more informative and actionable in the future. And most importantly, will make all possible cases to be resolved automatically.
Thank you. Issue resolved.
I am getting the same error recently. My thought was I could find the asset that has an old Last Price Update and that would be the trouble asset.
But I tried changing the price source field on the asset to a different ticker (just a random ticker for testing) but still get the Stale result error.
Can you suggest how I can fix this? The ticker I thought was erroneous was SPAXX (Fidelity Government Money Market Fund). Below is the error that appears.
Tried to fetch data too many times
Details:
{
"name": "PositionsDataError",
"dataErrors": {},
"fetchErrors": [
{
"name": "RetriesLimitError",
"message": "Tried to fetch data too many times",
"stack": "RetriesLimitError: Tried to fetch data too many times\n at _9 (https://app.mycapitally.com/assets/dedicated-worker-CiaRO-rv.js:253:22964)\n at async https://app.mycapitally.com/assets/dedicated-worker-CiaRO-rv.js:620:72151"
}
],
"message": "Positions failed to resolve"
}
Stack:
PositionsDataError: Positions failed to resolve
at Qh (https://app.mycapitally.com/assets/dedicated-worker-CiaRO-rv.js:253:20832)
at _9 (https://app.mycapitally.com/assets/dedicated-worker-CiaRO-rv.js:253:22954)
at async https://app.mycapitally.com/assets/dedicated-worker-CiaRO-rv.js:620:72151
Hey @Stuart_Davidson , the error you’re getting is a different one, related to the change I’ve made recently. It shouldn’t happen repeatedly, so if you’re getting it, it means there’s a bug.
First, can you try resetting the prices cache in Settings / Analysis?
If that doesn’t help, could you send me an anonymized project to support@mycapitally.com?
Resetting prices cache looks to have resolved it. Thank you.