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.
MyCurator should run automatically in the background without you doing anything, posting content that you can review in the Training Posts in the Admin or your Training page. If nothing is showing up, then this article will help you figure out what is wrong and what you can do to fix it.
One of the best features of MyCurator is that it runs in the background, discovering content and pushing it to your training page throughout the day. To do this, MyCurator uses a core part of WordPress called WP-Cron which wakes up when traffic comes to your site and looks for things to do such as run MyCurator, take out the Trash and implement scheduled posts.
The problem comes when you don’t have enough traffic on a regular basis to trigger WP-Cron. This is especially true if you are just starting out, or are trying out MyCurator on a test site. Without consistent traffic, the WordPress Cron will not wake up and check for things to do, so your Every 3 Hours schedule of running MyCurator won’t happen. In fact it will tend to run when you go to the site and check it out.