EagleGet Scheduler Not Working: Why Queued Downloads Never Start

A scheduler that never fires almost always has a boring cause: the program was not running, the schedule window was not what you thought it was, or the tasks were never actually queued. This post checks those causes before concluding that the scheduler is broken, because a scheduler cannot run tasks for a program that is closed.

Check 1: Is EagleGet running at the scheduled time?

The scheduler is part of EagleGet, not part of Windows. If EagleGet is closed at the scheduled time, nothing happens — there is no background service to wake it up. Either leave EagleGet running, or set it to start with Windows so it is present when the window opens. If you shut the computer down or let it sleep through the window, scheduled tasks will also not run; a sleeping computer does not download.

Check 2: Are the tasks actually queued?

A task that was never added to the queue cannot be scheduled, and a task that already finished, failed permanently, or was removed will not run either. Open EagleGet and confirm the tasks are listed, queued, and not marked as completed or failed. A common mistake is adding links and assuming they are scheduled, when they were actually added as immediate tasks that already tried — and failed — hours earlier.

Check 3: Is the time window set the way you think?

Verify the scheduler’s start and stop times, and check for AM/PM mistakes, which are the classic scheduling error. Also check whether a speed limit or a “do not download during this period” setting is overriding the window you set. If the window is short and the tasks are large, the window may simply have closed before the queue finished — that looks like “the scheduler did not work” but is actually “the window was too small.”

Check 4: Is something else blocking the downloads?

If tasks start but immediately fail, the scheduler is working and the downloads are failing for another reason — an expired link, a server refusal, or a full disk. See eagleget-unknown-network-error and eagleget-403-forbidden-error for those cases. Do not keep rescheduling a task that fails for a link reason; fix the link first.

A note on unattended downloads

Scheduling downloads to run while you are away is convenient, but unattended downloading has risks worth stating plainly: a large queue can fill a drive, a scheduled shutdown can interrupt other work, and a task set to run overnight will keep the computer awake. Set the post-queue behaviour deliberately, make sure the destination drive has room for the whole queue, and do not schedule downloads from sources you have not already tested with a small file.

FAQ

Does the scheduler work if I log out of Windows?

No. Logging out closes user programs, including EagleGet. The scheduler needs a logged-in session with EagleGet running.

Why did only some scheduled tasks run?

Usually the window closed before the queue finished, or later tasks failed on expired links while earlier ones succeeded. Check the task list for which tasks ran and which failed, rather than treating the whole queue as one outcome.

Can I schedule downloads for a time when the computer is off?

No. A powered-off computer cannot download. If you need overnight downloads, the computer must stay on (or at least awake) with EagleGet running.

Is there a way to get notified when a scheduled queue finishes?

EagleGet’s completion options depend on the version and settings available in your install. Do not rely on a notification you have not tested — run a small scheduled test first and confirm what actually happens when the queue ends.

Download EagleGet from the EagleGet download hub.