Calibre News Download Schedule Not Running: How to Fix It

When a calibre news download schedule is not running, the cause is usually one of a few things: calibre was not running at the scheduled time, the computer was asleep, the schedule was saved incorrectly, the news recipe failed, or calibre could not reach the source or write the finished e-book to the library. The fastest way to solve the problem is to separate a scheduling failure from a news-download failure. Start with one small manual test, check the resulting job details, and stop changing settings as soon as the test identifies the failing stage.

1. Confirm the Symptom With a Small Safe Test

Before editing schedules, reinstalling calibre, changing plugins, or moving your library, confirm exactly what is failing. A scheduled news job has several stages: the scheduler starts the job, calibre connects to the news source, the recipe gathers articles, calibre converts the content into an e-book, and the resulting publication is added to the active library. Optional delivery to a device or email address happens afterward.

1.1 Test the News Source Manually

Keep calibre open and make sure the computer has a working internet connection. Open the Fetch news menu, find the same news source used by the schedule, and start a manual download. Use a source that normally finishes quickly, if possible.

Watch the Jobs indicator in the lower-right area of the calibre window. A running job proves that calibre can start the recipe. When it finishes, look for the downloaded publication in the current library.

• If the manual download succeeds: The recipe, network connection, conversion process, and library are probably usable. Focus on the schedule, whether calibre remains running, and computer sleep.
• If the manual download fails: The schedule is not the primary problem. Open the failed job details and troubleshoot the recipe, credentials, network, conversion, or library error.
• If the job succeeds but no book appears: Confirm that you are viewing the same physical library in which the job ran. Clear searches and virtual-library filters before concluding that the publication is missing.

Success at this stage means the news e-book appears in the active calibre library without requiring a connected reader. Once that happens, stop changing recipe, conversion, and library settings. Continue only with scheduling checks.

1.2 Test All Scheduled Sources on Demand

The Fetch news menu also includes an option to download all scheduled news sources immediately. This is useful when the individual recipe works but you want to confirm that calibre recognizes it as scheduled.

If the source is absent from the scheduled batch, reopen its scheduling dialog and verify that scheduling is enabled. If the batch starts and succeeds, the remaining problem is usually that the normal trigger time occurs while calibre is closed, the computer is asleep, or the network is unavailable.

2. Check the Calibre Settings Directly Related to Scheduled News

2.1 Keep the Main Calibre Application Running

Calibre's built-in news schedule is part of the main graphical application. The computer must be powered on, the operating system must be awake, and calibre must be running when the scheduled job needs to start. Closing the calibre window may exit the application rather than leave a background scheduler active.

Do not assume that the presence of a calibre library, a connected reader, or a running Content server means the graphical news scheduler is active. If you normally close calibre after managing books, leave it open for a controlled test. You can minimize it or start it in the system tray where supported, but confirm through the operating system that the process is still running.

Success looks like a news job appearing in the Jobs area at the next scheduled time. Once you see that happen, stop adjusting the recipe and schedule. The original cause was that calibre was not active when the trigger occurred.

2.2 Recheck the Schedule for the Exact News Source

Open Fetch news, choose the scheduling option, and select the affected source. Check every scheduling field rather than relying on memory.

• Confirm that automatic downloading is enabled for that source.
• Verify the selected days of the week or interval between downloads.
• Check the scheduled time, including morning versus evening.
• Confirm that you edited the intended built-in or custom news source.
• Review any source-specific advanced options or account credentials.
• Save the settings before closing the dialog.

For a practical test, temporarily schedule the source a few minutes in the future. Leave calibre visible, prevent sleep, and keep the network connected. Do not set the test for the current minute because the trigger may already have passed by the time the dialog closes.

If the job starts at the new time, the scheduler works. Restore your preferred schedule and stop troubleshooting. If it does not start, confirm the system clock, time zone, and whether calibre remained open throughout the test.

2.3 Check the Computer Clock and Time Zone

Calibre relies on the operating system's time. An incorrect clock, time zone, or daylight-saving adjustment can make a valid schedule run at an unexpected hour. This is especially relevant after travel, dual-booting, restoring a virtual machine snapshot, or changing regional settings.

Correct the operating system time and time zone, restart calibre, and create another near-future test. Success means the job enters the queue at the expected local time. If it does, no recipe or library repair is needed.

2.4 Separate Downloading From Delivery

A connected e-reader is not required for calibre to download news. Normally, the completed news e-book is added to the library first. If a supported reader is connected when the download finishes, calibre may also send the publication to it. Email delivery is another separate step.

If the news book appears in the library but not on the device, the schedule worked. Troubleshoot device detection, USB transfer, or email delivery separately. Do not keep changing the schedule.

For email delivery, check the address configured under calibre's email-sharing preferences, the preferred format for that address, SMTP account settings, provider authentication requirements, and any rejection message. A mail failure does not necessarily mean the news fetch failed.

3. Check Sleep, Network, Permissions, and Library Availability

3.1 Prevent Sleep During the Test

A sleeping or hibernating computer cannot run an ordinary calibre GUI job at the scheduled moment. Screen lock is usually different from sleep, but power plans can put the machine to sleep shortly after the display turns off.

Temporarily set the computer to remain awake long enough to cover the test schedule. Laptop users should also check whether closing the lid triggers sleep. On macOS, review the relevant battery and power settings. On Windows, check the active power plan. On Linux, review desktop power management and any system sleep timers.

If the job starts while sleep is disabled, the calibre issue is resolved. Adjust the schedule to a time when the computer is normally awake, or configure a safe operating-system wake and startup routine. Avoid leaving a laptop running inside a closed bag because of heat risk.

3.2 Confirm Network Availability at the Scheduled Time

A news recipe needs internet access when it runs. Wi-Fi may disconnect during sleep, a VPN may not reconnect after wake, a captive portal may require browser confirmation, or a corporate proxy may block the source.

At the planned time, open the news site in a browser and then run the same source manually in calibre. If the browser works but calibre fails, inspect the job details for DNS, proxy, certificate, timeout, authentication, or HTTP errors. If both fail, repair the network connection before changing calibre.

Firewall or antivirus software can also interfere with outbound connections or calibre's temporary files. Do not permanently disable security software as a first step. Instead, review its logs and, if appropriate, create a narrow allow rule for the installed calibre application. Re-enable normal protection immediately after any controlled test.

3.3 Make Sure the Library Is Writable and Available

The news job must be able to create temporary files and add the finished book to the active library. Problems are more likely when the library is stored in a cloud-synchronized folder, network share, removable drive, or location controlled by another account.

• Confirm that the library drive is mounted and has free space.
• Make sure your user account can create and modify files there.
• Pause aggressive cloud synchronization during one test.
• Avoid opening the same library for writing from multiple computers.
• Check whether antivirus or backup software is locking files.
• Verify that calibre can add an ordinary test book to the library.

If a manual news fetch works in a local test library but fails in the normal library, the schedule is not the cause. Investigate the normal library's location, permissions, file locking, or database access. Do not delete the library or its metadata database as a speculative fix.

3.4 Treat Source and Credential Failures as Recipe Problems

News sites change layouts, feeds, login systems, subscription rules, and bot protections. A recipe that worked previously can therefore fail even though the schedule starts correctly. Job messages mentioning login failure, missing feeds, forbidden access, unexpected page content, or no articles usually point to the source or recipe.

Re-enter legitimate account details in the source's scheduling options where supported. Confirm that the subscription works in a normal browser and that the requested content is included in your account. This troubleshooting should not involve bypassing access controls or retailer restrictions.

If another built-in news source downloads successfully on the same computer, calibre's scheduler and basic network access are functioning. Stop changing global settings and concentrate on the affected source.

4. Use Job Details and Debugging Without Guessing

4.1 Open the Failed Job Details

When a job fails, open calibre's Jobs window and view its details. The final lines often identify the stage that failed. Read the error from the bottom upward, then look slightly earlier for the first specific failure.

• Connection or timeout errors: Test the network, DNS, VPN, proxy, and source availability.
• Authentication errors: Recheck the supported username, password, and subscription access.
• Permission denied errors: Check temporary-folder and library permissions.
• No articles or empty feed messages: Test the source in a browser and consider a recipe problem.
• Conversion errors: Retest with default news output settings and inspect the complete job log.
• Database or library errors: Switch to a local temporary library for comparison.

Copy the details before closing the window if you may need support. Remove email addresses, usernames, tokens, cookies, and other private information before sharing a log publicly.

4.2 Start Calibre in Debug Mode When Necessary

If no job appears at the scheduled time and the ordinary interface provides no useful explanation, launch calibre from a terminal or command prompt with debugging enabled by using calibre-debug -g. Keep that terminal open while reproducing the issue.

Use this step only after confirming that calibre is running, the schedule is enabled, and the computer is awake. Debug output can reveal startup, configuration, plugin, or scheduling errors that are not obvious in the normal interface.

A debug session is successful when it produces a specific, repeatable error or when the scheduled job starts normally. If it starts normally in debug mode, compare how calibre was launched during the failed test, including the user account, library path, startup shortcut, and environment.

4.3 Test Without Custom Plugins

Most scheduled-news failures are not caused by unrelated device, metadata, viewer, or editor plugins. However, a plugin that disrupts calibre startup or the job system can complicate diagnosis.

Temporarily start calibre with custom plugins ignored by using the documented --ignore-plugins option. Then repeat the near-future schedule test. Do not uninstall every plugin at once.

If the schedule works with custom plugins ignored, re-enable normal operation and disable recently installed or updated plugins one at a time. If nothing changes, restore the plugins and move on. Viewer and editor behavior is generally irrelevant unless the news book downloads successfully but cannot be opened afterward.

5. Run a Clean Temporary Test Before Reinstalling

Reinstalling calibre usually does not correct a missed schedule caused by sleep, a closed application, bad source credentials, or an unavailable library. A clean comparison test provides more information with less risk.

1. Create or switch to a new empty library in a local folder owned by your user account.
2. Keep the original library untouched.
3. Select one simple built-in news source that does not require a login.
4. Run it manually and confirm that a publication is added.
5. Schedule it several minutes in the future.
6. Leave calibre running, keep the computer awake, and maintain the network connection.
7. Watch the Jobs indicator when the scheduled time arrives.

If the clean test succeeds, calibre's core scheduler works. Compare the original source, schedule, library location, credentials, plugins, and launch method one variable at a time. If the clean test fails and no job starts, collect debug output before considering an update or reinstall.

Do not delete your normal library, configuration folder, or metadata.db file as a general troubleshooting experiment. Back up the library before making structural changes.

5.1 Consider Headless or Server Automation Separately

The calibre Content server shares books from a library, but it should not be treated as a replacement for the main GUI's scheduled-news function. Running only the server does not provide the same built-in desktop scheduling workflow.

For an always-on or headless Linux system, calibre provides command-line tools that can download and convert a news recipe, add the resulting file to a library, and send mail. The operating system's scheduler, such as a systemd timer or cron job, must then start those commands. This is a separate automation design rather than a repair to the GUI schedule.

Windows Task Scheduler and macOS launch services can also start applications or scripts, but command-line automation requires careful paths, output filenames, credentials, permissions, and library locking. Nontechnical users will usually get a more reliable result by leaving the main calibre application running at a time when the computer is awake.

6. Quick Fix Checklist

• Leave the main calibre application running at the scheduled time.
• Keep the computer awake and connected to the internet.
• Run the affected news source manually.
• Confirm that manual output appears in the active library.
• Open failed job details and read the first specific error.
• Recheck the source's enabled days, interval, time, and credentials.
• Schedule a controlled test several minutes in the future.
• Verify the operating system clock and time zone.
• Separate library download success from device or email delivery.
• Test a local temporary library if the normal library is synchronized or remote.
• Use calibre-debug -g only when ordinary logs are insufficient.
• Test without custom plugins before reinstalling calibre.

The most useful stopping rule is simple: once the job starts on schedule and the resulting publication appears in the library, the scheduled-news problem is fixed. Any remaining device, email, formatting, viewer, or delivery problem should be handled separately.

7. Frequently Asked Questions

7.1 Does Calibre Need to Be Open for Scheduled News Downloads?

Yes. The built-in scheduled-news workflow depends on the main calibre application running. The computer must also be awake. Minimizing calibre is acceptable if the process remains active, but fully exiting it prevents the GUI scheduler from starting the job.

7.2 Will Calibre Run a Missed News Download After the Computer Wakes?

Do not rely on a missed trigger being recovered exactly as expected. For predictable operation, schedule the job for a time when the computer is normally awake, calibre is already running, and the network is connected. Use an operating-system automation method if you need stricter unattended execution.

7.3 Why Does Manual News Download Work but the Schedule Does Not?

This result usually means the recipe, conversion process, network connection, and library are functional. Check whether scheduling is enabled for the correct source, whether the chosen time and days are correct, and whether calibre was running while the computer was awake at that time.

7.4 Why Is the News Book in Calibre but Not on My Reader?

The schedule succeeded if the book is present in the library. Device delivery is a later step. Check whether the reader was connected and detected when the download finished, whether its USB mode allows file transfer, whether the format is supported, and whether automatic sending is configured as expected.

7.5 Can the Content Server Download Scheduled News Without the GUI?

The Content server is primarily for providing access to books in a calibre library. It is not a direct substitute for the main application's scheduled-news system. A headless setup normally uses calibre command-line utilities together with an operating-system scheduler.

7.6 Should I Reinstall Calibre When Scheduled News Stops Working?

Not initially. First run a manual news download, inspect the job details, verify the schedule, prevent sleep, and test in a temporary local library. Reinstallation is reasonable only when a clean test also fails and the logs indicate damaged or missing application components. It will not repair an incorrect schedule, unavailable website, sleeping computer, blocked network, or unwritable library.