XML Sitemap is not getting updated when automated cron is run. Still getting page not found error.

I have the same issue. Have you found the cause and solution?

I have the same problem. But I think the isse is to expose the sitemap fields used to the anonymous user. It certainly overcame access to robotstxt module becoming exposed to search consoles at Bing and Google

Oddly, our site was also not regenerating the xml sitemap during drupal's cron. Here's the correct crons for an Acquia Next site:

Default schedueld task:
```
/usr/local/bin/cron-wrapper.sh site.environment https://yoursite.com &>> /shared/logs/default-drush-cron.log
```
xml sitemap regeneration scheduled task:
```
cd /var/www/html/${AH_SITE_NAME}/docroot && drush xmlsitemap:regenerate &>> /shared/logs/xmlsitemap.log
```

Edit: markdown when, drupal.org?

I am facing the same issue on the site. However it only occurs intermittently and very difficult to reproduce and ascertain the root cause.

We also see this on a site with > 50K links. Sometimes it generates 3 sitemap pages with exactly 10K links each, sometimes 2, sometimes none. When run manually from drush, it generates 6 pages, the first 5 10K links and the remainder on the 6th. But doing this today took 1 hour 24 minutes to complete...

We might try the workaround suggested -- disabling the cron generation and adding our own drush cron job... or give simple_sitemap a try.

I'm also experiencing that cron is not reliable. In my case when I unpublished some node in EN language, in meantime cron regenerated the sitemap then I unpublished the other language version of the same node, then the cron simply did not include that change into the other language sitemap. Walk-around will be setting cron drush command to rebuild the sitemap. I do not want invest more time into investigating that.

Note that you can adjust at
/admin/config/search/xmlsitemap/settings
I set it to process only 50 items at once rather than the default 100, and it now successfully completes.

Actually, that wasn't working reliably. But throwing this into a custom module seems to be working:

/**
 * Implements hook_cron().
 */
function mymodule_cron() {
  $logger = Drupal::logger('mymodule);
  $logger->info('Starting `drush xmlsitemap:rebuild` asynchronously.  It will take about 10 minutes to complete.');
  pclose(popen("drush xmlsitemap:rebuild &","r"));
}

I wonder if we should roll this into the module as an option:
* Run as a normal cron hook
* Run as an asynchronous cron hook (requires drush)
* Don't run during cron