Closed jfm5248 closed 1 year ago
Hey @jfm5248
Just to say thanks for raising this issue and to let you know that we've labelled it as a heartcore issue so that the right people see it.
Emma
We seem to have the same exception too.
There is an async Task in background, to import product nodes in Umbraco. Every now and then, we get this exception when doing stuff like contextRef.UmbracoContext.Content.GetByXPath
After doing Published Status -> Caches -> Internal -> Collect
The error is gone.. But after a while it is back again... Really annoying, as we don't know what to do about this..
Hiya @jfm5248,
Just wanted to let you know that we noticed that this issue got a bit stale and might not be relevant any more.
We will close this issue for now but we're happy to open it up again if you think it's still relevant (for example: it's a feature request that's not yet implemented, or it's a bug that's not yet been fixed).
To open it this issue up again, you can write @umbrabot still relevant
in a new comment as the first line. It would be super helpful for us if on the next line you could let us know why you think it's still relevant.
For example:
@umbrabot still relevant This bug can still be reproduced in version
x.y.z
This will reopen the issue in the next few hours.
Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:
@umbrabot still relevant I am seeing this problem in version 13.1.0 after a failed import of content via ContentService. I have not been able to resolve the issue. The exception is encountered when trying to enumerate the children of a node.
We started getting this error in our Dev environment last Friday when calling https://cdn.umbraco.io/content/{id}/descendants for a particular ID.
Going into the backoffice and rebuilding the DB cache and reloading the memory cache resolved it.
I have no idea what triggered this issue or how to reproduce it as this had been working and the node we were calling descendants on isn't new. I assume the issue may have been caused by Umbraco-managed upgrades or infrastructure changes that have been going on.
Umbraco version
Heartcore (whichever version is in Dev as of this writing).
Expected result
I should be able to reliably get content from the CMS.
Actual result
Headless API randomly broke, which took down our website in Dev (thankfully not production) until we manually reloaded Umbraco's cache.