- Issue created by @davidiio
- 🇳🇱Netherlands megachriz
Is the feeds_item field missing? And an explanation about what the hash is
Based on the error message it could be that on the entity to be imported the field "feeds_item" is missing. This field is used to track metadata about an import: which feed the content is imported with, when the last import happened and a hash of the item that was imported last. The hash is used to determine if a source item has changed since the last import.
If a missing feeds_item is indeed the cause (not too sure about that, because I would have expected a different error message in that case), then that can be fixed by resaving the feed type. The feeds_item field will then be recreated.
Are you using multiple feeds to update the same content?
If a missing feeds_item is not the cause, then I'm wondering if you are using multiple feeds to update the same content? Because I did notice recently that something with the feeds_item field's data happened that didn't look right when I used two feeds to update the same content: a reference to one feed was kept, but a reference to the other feed was missing. But I haven't investigated yet if that bug is caused by Feeds or a custom module on the site.
Why the hash should be reset
A hash on the feed item is reset to
NULLwhen a referenced entity cannot be found. If Feeds wouldn't reset it, the item won't be updated on a subsequent import, even if the referenced entity is available then.
🐛 Feed items are constantly updated due to missing entity reference Active is indeed about accepting that some references don't exist and stop updating these entities every import. - 🇵🇹Portugal jrochate
I was having this same problem.
Even forcing to update records on every run, this error always poped-up.
I found out that when a referenced entity did not exists, instead of feeds reporting that (as usual) it would break.
I solved it by guarantying that the referenced entity always exists before running the feed that was rising the error.
Maybe this can be helpful to anyone who comes here with the same problem: be sure that referenced entities (nodes) already exists.