[Bug]: Podcast scheduled updates not working anymore. #2804

Closed
opened 2026-04-25 00:10:47 +02:00 by adam · 8 comments
Owner

Originally created by @zen85 on GitHub (May 26, 2025).

What happened?

My Podcast episodes suddenly dont update anymore. and so my "latest episodes" is not updating anymore. it seems the scheduling is not working anymore. i updated everything but no change. i restarted the docker but no change.

but when i click "check for new episodes" in my podcasts library for each it works fine. it is supposed to update every hour.

I dont really know where and how i can debug this. did anyone experience something similar or has an idea how to get into this?

What did you expect to happen?

this behaviour started suddenly for no apparent reason. i expect the scheduler to look for new episodes to work.

Steps to reproduce the issue

i found no way to reproduce.

Audiobookshelf version

2.23

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

If the issue is being seen in the UI, what browsers are you seeing the problem on?

None

Logs


Additional Notes

No response

Originally created by @zen85 on GitHub (May 26, 2025). ### What happened? My Podcast episodes suddenly dont update anymore. and so my "latest episodes" is not updating anymore. it seems the scheduling is not working anymore. i updated everything but no change. i restarted the docker but no change. but when i click "check for new episodes" in my podcasts library for each it works fine. it is supposed to update every hour. I dont really know where and how i can debug this. did anyone experience something similar or has an idea how to get into this? ### What did you expect to happen? this behaviour started suddenly for no apparent reason. i expect the scheduler to look for new episodes to work. ### Steps to reproduce the issue i found no way to reproduce. ### Audiobookshelf version 2.23 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? None ### Logs ```shell ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:10:47 +02:00
adam closed this issue 2026-04-25 00:10:47 +02:00
Author
Owner

@zen85 commented on GitHub (May 26, 2025):

i just found some logs.
the scheduler runs as expected but it does not find new episodes.
apparently a podcast that definetly had new episodes said "up to date" but only found them when i manually triggered "Check & Download for new Episodes"

@zen85 commented on GitHub (May 26, 2025): i just found some logs. the scheduler runs as expected but it does not find new episodes. apparently a podcast that definetly had new episodes said "up to date" but only found them when i manually triggered "Check & Download for new Episodes"
Author
Owner

@advplyr commented on GitHub (May 26, 2025):

Can you share the logs? On the logs page make sure you have Debug logs selected first, then let the auto downloaded run.
There should be details in the logs about the timestamp it is using to compare the episodes.

@advplyr commented on GitHub (May 26, 2025): Can you share the logs? On the logs page make sure you have Debug logs selected first, then let the auto downloaded run. There should be details in the logs about the timestamp it is using to compare the episodes.
Author
Owner

@zen85 commented on GitHub (May 27, 2025):

i uploaded a full log file here https://josefwagner.net/logs.txt

the best example here is the podcast "Ö1 Journale" - there should be 4 episodes each day. whats really interessting is that there are no checks after these lines:

[podcastUtils] getPodcastFeed for "https://podcast.orf.at/podcast/oe1/oe1_journale/oe1_journale.xml" success - parsing xml

2025-05-27 02:00:25.868

DEBUG

[PodcastManager] runEpisodeCheck: N/A episodes found

2025-05-27 02:00:25.869

DEBUG

[PodcastManager] No new episodes for "Ö1 Journale"

2025-05-27 02:00:25.896

and therefor it did not find the new episodes.

another thing is: my timezone here is gmt+2 but all the logs are in gmt time but that should not matter i think.

@zen85 commented on GitHub (May 27, 2025): i uploaded a full log file here [https://josefwagner.net/logs.txt](url) the best example here is the podcast "Ö1 Journale" - there should be 4 episodes each day. whats really interessting is that there are no checks after these lines: [podcastUtils] getPodcastFeed for "https://podcast.orf.at/podcast/oe1/oe1_journale/oe1_journale.xml" success - parsing xml 2025-05-27 02:00:25.868 DEBUG [PodcastManager] runEpisodeCheck: N/A episodes found 2025-05-27 02:00:25.869 DEBUG [PodcastManager] No new episodes for "Ö1 Journale" 2025-05-27 02:00:25.896 and therefor it did not find the new episodes. another thing is: my timezone here is gmt+2 but all the logs are in gmt time but that should not matter i think.
Author
Owner

@advplyr commented on GitHub (May 27, 2025):

First log I found for podcast download:

INFO

[PodcastManager] runEpisodeCheck: "Was tun, Herr General - Der Podcast zum Ukraine-Krieg" | Last check: Tue May 27 2025 00:00:04 GMT+0000 (Coordinated Universal Time) | No latest episode

2025-05-27 01:00:06.514

DEBUG

[PodcastManager] runEpisodeCheck: "Was tun, Herr General - Der Podcast zum Ukraine-Krieg" checking for episodes after Tue May 27 2025 00:00:04 GMT+0000 (Coordinated Universal Time)

2025-05-27 01:00:06.515

DEBUG

[podcastUtils] getPodcastFeed for "https://www.mdr.de/nachrichten/podcast/general/russland-angriff-krieg-ukraine100-podcast.xml"

Notice this log: "Was tun, Herr General - Der Podcast zum Ukraine-Krieg" checking for episodes after Tue May 27 2025 00:00:04 GMT+0000 (Coordinated Universal Time)

Now when I open that RSS feed I can see the latest episode was released 7 days ago

Image

Abs is looking for episodes after Tue May 27 2025 00:00:04 GMT+0000 which there is none, so that is correct.

When Abs does a check for new episodes it will check for the episode you already have with the latest pub date. If you don't have any episodes it will use the last date it checked.

Maybe you have no downloaded any episodes yet so it doesn't have a good date to use?

@advplyr commented on GitHub (May 27, 2025): First log I found for podcast download: ``` INFO [PodcastManager] runEpisodeCheck: "Was tun, Herr General - Der Podcast zum Ukraine-Krieg" | Last check: Tue May 27 2025 00:00:04 GMT+0000 (Coordinated Universal Time) | No latest episode 2025-05-27 01:00:06.514 DEBUG [PodcastManager] runEpisodeCheck: "Was tun, Herr General - Der Podcast zum Ukraine-Krieg" checking for episodes after Tue May 27 2025 00:00:04 GMT+0000 (Coordinated Universal Time) 2025-05-27 01:00:06.515 DEBUG [podcastUtils] getPodcastFeed for "https://www.mdr.de/nachrichten/podcast/general/russland-angriff-krieg-ukraine100-podcast.xml" ``` Notice this log: `"Was tun, Herr General - Der Podcast zum Ukraine-Krieg" checking for episodes after Tue May 27 2025 00:00:04 GMT+0000 (Coordinated Universal Time)` Now when I open that RSS feed I can see the latest episode was released 7 days ago <img width="659" alt="Image" src="https://github.com/user-attachments/assets/0cde7743-d472-4a11-859c-f649d624a908" /> Abs is looking for episodes after `Tue May 27 2025 00:00:04 GMT+0000` which there is none, so that is correct. When Abs does a check for new episodes it will check for the episode you already have with the latest pub date. If you don't have any episodes it will use the last date it checked. Maybe you have no downloaded any episodes yet so it doesn't have a good date to use?
Author
Owner

@Eragos commented on GitHub (May 30, 2025):

Hey @advplyr

I'm searching for a similar thing actually:

  • Over the week there were 5 or 6 missing episodes.
  • If I pull/check them manualy I got them.

Image

In the Logs I see only:
Image

  • I just started with audiobookshelf and I really like it ❤️
  • I switched the log level to debug get a more usable output.
  • I saw similar than in the last screenshot.

Image

Version: v2.23.0
Docker based
Clients: MacOS / iOS but this doesn't matter ;-)

Hope it helps a bit...

Best Michael

@Eragos commented on GitHub (May 30, 2025): Hey @advplyr I'm searching for a similar thing actually: - Over the week there were 5 or 6 missing episodes. - If I pull/check them manualy I got them. ![Image](https://github.com/user-attachments/assets/26d367c5-ddf3-47b2-a29f-81281536af52) In the Logs I see only: ![Image](https://github.com/user-attachments/assets/5caf2582-25c6-4727-8e26-d6aee7eca139) - I just started with audiobookshelf and I really like it ❤️ - I switched the log level to debug get a more usable output. - I saw similar than in the last screenshot. ![Image](https://github.com/user-attachments/assets/c9f45e41-5c6a-48b5-9bb0-274df9f50739) > Version: v2.23.0 > Docker based > Clients: MacOS / iOS but this doesn't matter ;-) Hope it helps a bit... Best Michael
Author
Owner

@advplyr commented on GitHub (Jun 1, 2025):

@Eragos That seems to be a different issue. Reported here https://github.com/advplyr/audiobookshelf/issues/4098. That hasn't been reproducible yet

As for this issue, this doesn't appear to be a bug with the information provided as I explained here https://github.com/advplyr/audiobookshelf/issues/4339#issuecomment-2912551825

@advplyr commented on GitHub (Jun 1, 2025): @Eragos That seems to be a different issue. Reported here https://github.com/advplyr/audiobookshelf/issues/4098. That hasn't been reproducible yet As for this issue, this doesn't appear to be a bug with the information provided as I explained here https://github.com/advplyr/audiobookshelf/issues/4339#issuecomment-2912551825
Author
Owner

@zen85 commented on GitHub (Jun 3, 2025):

thank you all so far

but.... there still is a bug involved... your explanation just described the expected behaviour for one podcast.

I had 43 in my library that did not update.

they inded stop updating and its the same issue in my logs as it is with Eragos and it can be looked up in my logs too. its the same problem. something happens and a cron-job does not finish and then it never runs again. (see the warnings - i have the same as eragos)

I could solve it by giving every item in my library an unique cronjob by giving each a different time in the hope to find the faulty podcast - but now all of them update as expected and i have no warnings anymore.

something fishy is indeed going on here :)

@zen85 commented on GitHub (Jun 3, 2025): thank you all so far but.... there still is a bug involved... your explanation just described the expected behaviour for one podcast. I had 43 in my library that did not update. they inded stop updating and its the same issue in my logs as it is with Eragos and it can be looked up in my logs too. its the same problem. something happens and a cron-job does not finish and then it never runs again. (see the warnings - i have the same as eragos) I could solve it by giving every item in my library an unique cronjob by giving each a different time in the hope to find the faulty podcast - but now all of them update as expected and i have no warnings anymore. something fishy is indeed going on here :)
Author
Owner

@advplyr commented on GitHub (Jun 3, 2025):

Yeah there is a bug somewhere but no one has figured out how to reproduce it yet. I have podcast crons still running from years ago at this point. The open issue for what you are describing is #4098

@advplyr commented on GitHub (Jun 3, 2025): Yeah there is a bug somewhere but no one has figured out how to reproduce it yet. I have podcast crons still running from years ago at this point. The open issue for what you are describing is #4098
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2804