At the end of a PodcastImport when the last episode completes, we unlock the Feeder podcast so it will start publishing the RSS to S3 again.
In reality, there are still a ton of audio/image callbacks coming into CMS that will trigger subsequent updates. Not to mention all the async processing/callbacks going on in feeder itself. For large imports, this tends to cause thousands+ of PublishFeedJobs to stack up in Feeder. And nearly all of them are redundant.
Instead, let's keep the podcast locked for longer. Bad ideas:
Try to guesstimate in CMS or Feeder when the "last" update from the import comes through.
Set a timer for 10/15/30/something minutes, and then unlock/publish the feed.
Make it manual - maybe you have to click "unlock" on the Publish UI?
At the end of a PodcastImport when the last episode completes, we unlock the Feeder podcast so it will start publishing the RSS to S3 again.
In reality, there are still a ton of audio/image callbacks coming into CMS that will trigger subsequent updates. Not to mention all the async processing/callbacks going on in feeder itself. For large imports, this tends to cause thousands+ of
PublishFeedJobsto stack up in Feeder. And nearly all of them are redundant.Instead, let's keep the podcast locked for longer. Bad ideas: