Website Content Crawler

I have three Website Content Crawler jobs that run every Saturday night. Last week, one of the three jobs mysteriously failed to crawl anything or return any results. Its full log:

12024-06-30T00:03:30.322Z ACTOR: Pulling Docker image of build cxepl9SPHv3B0GfJ2 from repository.
22024-06-30T00:03:30.463Z ACTOR: Creating Docker container.
32024-06-30T00:03:51.362Z ACTOR: Starting Docker container.
42024-06-30T00:03:55.108Z Starting X virtual framebuffer using: Xvfb :99 -ac -screen 0 1920x1080x24+32 -nolisten tcp
52024-06-30T00:03:55.109Z Executing main command
62024-06-30T00:03:58.629Z INFO  System info {"apifyVersion":"3.2.3","apifyClientVersion":"2.9.0","crawleeVersion":"3.10.3","osType":"Linux","nodeVersion":"v18.19.1"}
72024-06-30T00:03:59.116Z WARN  A non-zero value of the `dynamicContentWaitSecs` option is not supported by the Cheerio crawler.
82024-06-30T00:04:16.425Z INFO  HttpCrawler: Starting the crawler.
92024-06-30T00:04:16.802Z INFO  CheerioCrawler: Starting the crawler.
102024-06-30T00:04:16.910Z INFO  CheerioCrawler: All requests from the queue have been processed, the crawler will shut down.
112024-06-30T00:04:17.220Z INFO  CheerioCrawler: Final request statistics: {"requestsFinished":0,"requestsFailed":0,"retryHistogram":[],"requestAvgFailedDurationMillis":null,"requestAvgFinishedDurationMillis":null,"requestsFinishedPerMinute":0,"requestsFailedPerMinute":0,"requestTotalDurationMillis":0,"requestsTotal":0,"crawlerRuntimeMillis":16579}
122024-06-30T00:04:17.221Z INFO  CheerioCrawler: Finished! Total 0 requests: 0 succeeded, 0 failed. {"terminal":true}

(The warning about dynamicContentWaitSecs was new, and it seems like it's still documented as a valid input parameter.) Run URL: https://console.apify.com/actors/aYG0l9s7dbB7j3gbS/runs/HPbMHZufEn5eIfskb

Then this week, all three jobs failed in precisely the same way. Run URLs: https://console.apify.com/actors/aYG0l9s7dbB7j3gbS/runs/5tafMNrXeNUswOpXo, https://console.apify.com/actors/aYG0l9s7dbB7j3gbS/runs/Fn7JwjD3OGIcj171i, https://console.apify.com/actors/aYG0l9s7dbB7j3gbS/runs/3Ee1hY3mQWxqJ2KW4

This morning (about 13 hours after the three failed runs), I manually triggered a run and it started out fine. It gave the new warning, but it continued to crawl and return results. I then re-triggered my weekly process, which fired off its three runs via the API, and they all worked fine, despite including the new warning. One example run: https://console.apify.com/actors/aYG0l9s7dbB7j3gbS/runs/8zqZHm9xzcM3b1bfT

Any idea what's going on here? In addition to the crawls not working, they return success, so my automated processes think they succeeded when they in fact failed. It's caused some embarrassment here on my end.