Here's what I think is happening: the userFeedback table tracks feedback from users of Publication Manager that has not yet been added and looked up in the eSearchResults table. When we run Feature Generator, the userFeedback record gets cleared out in all cases.
Ideally, we would only do this when there are records in that table. Is there a way we can avoid this error? Do we have to delete it every time? It seems like a waste of resources. But maybe we do need to do this.
The ReCiter Connect logs display the below errors. Why are we trying to run jobs for people when they don't exist?
Here's what I think is happening: the userFeedback table tracks feedback from users of Publication Manager that has not yet been added and looked up in the eSearchResults table. When we run Feature Generator, the userFeedback record gets cleared out in all cases.
Ideally, we would only do this when there are records in that table. Is there a way we can avoid this error? Do we have to delete it every time? It seems like a waste of resources. But maybe we do need to do this.