If you run the MyCurator article collection process manually (Run AI Process button on “the Topics page) you may have seen an error message such as “internal server 500 error” or it just hangs up on the Topics page screen. Similarly if you look in the Logs – Process filter you may see the that the background process just stops without reading all of the Topics or Sources. What is happening?
In version 2.1 of MyCurator we introduced a new background process called Request Processing. How do I know if I need to use it for my site? The short answer is that it will probably benefit every site.
If you ever look in your Error Log then you have probably seen the message Error Rendering Page. This post discusses why this error happens and some things you can do about it.
You see that articles are being posted on the web site, but nothing is coming through to your training pages or posts on MyCurator! This post will walk you through a step-by-step process to figure out why and what to do about it.
When you go to curate content from your training posts, it seems that you aren’t seeing the articles that you think you should. Maybe you’ve seen some posts on a blog whose RSS is in your sources, yet they don’t show up in the Training page. Or you’ve go some Google Alerts but they don’t seem to bring anything back, yet a search of the keywords shows some results.