AIMP Scheduler Not Running: How to Fix It

When the AIMP scheduler is not running, the failure usually belongs to one of five categories: the task is disabled or configured with the wrong trigger, AIMP is not running when the trigger arrives, Windows cannot wake the computer, the selected playlist or stream is unavailable, or the Scheduler plugin has been disabled or failed to load. On Android, there is an additional distinction: current AIMP releases provide a sleep timer, not the full Windows-style Scheduler with recurring alarm and automation tasks.

The safest approach is to create a small one-minute test, confirm exactly which part fails, and change one setting at a time. Once the test succeeds, stop changing settings and apply the same configuration to the real task.

1. Confirm the Symptom With a Small Safe Test

Do not begin with your normal morning alarm, shutdown action, radio recording, or complicated weekly schedule. A short test tells you whether the scheduling engine itself works without risking lost playback, an unexpected shutdown, or an overwritten recording.

1.1 Create a one-minute playback task

On AIMP for Windows, open the Scheduler and create a temporary task scheduled for approximately one minute in the future. Choose a simple playback action using a short local audio file that already plays correctly when opened manually.

1. Keep AIMP open and visible.
2. Confirm the computer is awake and unlocked for this first test.
3. Enable the task after creating it.
4. Set the Windows and AIMP volume to an audible level.
5. Wait without editing the task or changing the system clock.

Success means the selected local file begins playing at the expected time. If that happens, the Scheduler is functioning. Stop changing Scheduler or plugin settings and investigate the source used by the original task, such as its playlist, radio URL, network path, or output device.

If nothing happens, leave the test task in place temporarily and continue with the checks below.

1.2 Separate trigger failure from action failure

A task can trigger correctly while its requested action fails. For example, the Scheduler may run but select an empty playlist, resume a paused stream whose URL has expired, or send audio to a disconnected device.

Repeat the test with a second simple action, such as changing the volume or starting a known local track. If a volume action works but playback does not, the trigger is probably fine. Concentrate on the file, playlist, or audio output. If no action works, inspect the task state, trigger, AIMP process, and Scheduler plugin.

2. Check the Scheduler Task and Trigger

2.1 Verify that the task is enabled

A saved task is not necessarily active. Open the task list and confirm that the relevant task has its enabled state selected. This is especially important after editing, duplicating, importing, or testing a one-time task.

Some one-time configurations are no longer useful after their scheduled moment passes. If the displayed next-run time is missing or already in the past, edit the trigger and choose a future time. Success means the task remains enabled and shows a sensible upcoming run time.

2.2 Distinguish time triggers from event triggers

A time trigger runs at a specified clock time or after a defined interval. An event trigger waits for something else to happen, such as reaching the end of playback or completing another operation. Confusing the two can make a valid task appear broken.

If you expect an alarm at 7:00 AM, use a time-based trigger. If you expect AIMP to stop after the current playlist finishes, use the corresponding playback event. An event-based task will not fire merely because the clock reaches a particular time.

For diagnosis, replace the original trigger temporarily with a one-minute time trigger. If the action then works, the original event condition was never reached. Stop changing permissions or reinstalling AIMP and correct the event logic instead.

2.3 Review repeat schedule configuration

Check every part of a recurring schedule, including its start date, time, repeat interval, selected weekdays, and end condition. A weekly task can be enabled yet skip today because the current weekday is not selected. A daily task may also have an end date that has passed.

• For a daily alarm, confirm daily repetition rather than one-time execution.
• For weekdays, verify each intended day individually.
• For intervals during the day, inspect both the interval and permitted time range.
• For annual or monthly tasks, confirm the calendar date.
• Check Windows time, date, time zone, and daylight-saving configuration.

Success means the Scheduler displays the expected next occurrence. Once that value is correct, do not rebuild the task unless it still misses that occurrence.

3. Confirm That AIMP Can Execute the Task

3.1 Keep AIMP running

AIMP's Scheduler belongs to the application and is not the same as Windows Task Scheduler. For an AIMP task to execute, AIMP must normally remain running. Minimizing it to the notification area is fine, but choosing Exit closes the program and removes the process that would execute the task.

Open Task Manager shortly before the test and confirm that AIMP is listed. If it is absent, start AIMP and repeat the one-minute test. Success means the task works while AIMP stays open. At that point, the previous failure was caused by the application being closed, not by the playlist or audio engine.

If you need the task after every Windows restart, configure AIMP to start with Windows through an appropriate application or operating-system startup setting. Test that startup behavior by restarting Windows and confirming that AIMP is running before relying on the alarm.

3.2 Check the Scheduler plugin

On Windows, open AIMP's settings and inspect the installed plugins. Confirm that the Scheduler plugin is present, enabled, and loaded without an error. If the Scheduler button is unavailable or gray, a missing or disabled plugin is a direct suspect.

If AIMP reports that the Scheduler plugin raised an exception and was unloaded, do not repeatedly force it to load. Save a backup of your playlists and profile data, restart AIMP, and proceed to the temporary clean-profile test later in this guide.

Success means the Scheduler interface opens normally after an AIMP restart and the plugin remains enabled. Once it does, return to the one-minute task instead of changing unrelated plugins.

3.3 Test the default skin and essential plugins only

A skin normally changes presentation rather than scheduling logic, but a custom skin can hide a control or make its state difficult to interpret. Switch temporarily to an included AIMP skin and open the Scheduler through the application's menu or settings rather than relying only on a skin button.

Temporarily disable nonessential third-party plugins if AIMP crashes, freezes, or unloads the Scheduler. Do not remove plugins permanently during the first test. Success means the Scheduler remains available with the default skin and essential components. Re-enable optional plugins one at a time until the conflict returns.

4. Verify the Playlist, File, Stream, and Output Device

4.1 Open the scheduled source manually

If the task fires but produces no audible result, manually open the exact track, playlist, radio station, podcast item, cloud file, or network path selected by the task. Do not test a similar item.

For a playlist, confirm that it contains playable entries and that the referenced files have not been moved, renamed, deleted, or disconnected. A playlist can retain visible titles even when its underlying file paths are invalid.

For a local file, open its file information and verify its location and format. Tags and artwork rarely prevent the Scheduler from firing, but a damaged file, extremely large embedded image, inaccessible path, or malformed metadata can interfere with loading. Test with a small known-good MP3, FLAC, or WAV file to separate source quality from scheduling.

Success means the exact source starts immediately when selected manually. If it does not, stop modifying the Scheduler and repair or replace that source.

4.2 Inspect playlist and music library state

If the scheduled action points to a named playlist, make sure that playlist still exists and opens with the expected tracks. If it relies on music-library content, rescan the affected folders and confirm that AIMP still has access to them.

Create a temporary playlist containing one local file, then target that playlist in the one-minute task. If it works, rebuild the original playlist references or rescan the library. Do not delete all playlists. Back them up before making structural changes.

4.3 Check radio, podcast, cloud, WebDAV, and Samba sources

Network audio introduces failures that a local-file test will not reveal. The Scheduler may run while the remote source is offline, its URL has changed, credentials have expired, or the network is still reconnecting after sleep.

• Open the exact station or episode manually.
• Confirm that the computer has internet or local-network access.
• Re-enter cloud, WebDAV, or Samba credentials if authentication fails.
• Check whether a saved radio URL redirects to an unsupported webpage instead of an audio stream.
• Allow enough time for Wi-Fi and network storage to reconnect after wake.

Success means the remote source starts reliably several times without the Scheduler. Only then should you test it in a scheduled task.

4.4 Select a working audio output

AIMP may be playing correctly through an output you cannot hear. This commonly occurs after disconnecting USB speakers, turning off an external receiver, changing Bluetooth devices, or switching the Windows default playback device.

Open AIMP's playback or sound output settings and choose an available device. For diagnosis, use the Windows default output or the computer's built-in speakers. Confirm that AIMP is not muted in the Windows volume mixer.

Bluetooth devices can expose different profiles, and the profile available during the test may not be the one previously used by AIMP. Reconnect the device and test ordinary playback before testing the alarm. Success means a manually played track and the scheduled test use the same audible output.

5. Check Sleep, Hibernate, and Wake Behavior

5.1 Determine whether the task fails only during sleep

Run the one-minute test once while the computer remains awake. Then create a second test several minutes ahead, enable the task's wake option if available, and put the computer to sleep.

If the awake test works but the sleeping test does not, the Scheduler action and source are probably valid. Stop editing the playlist and focus on Windows power management.

5.2 Allow wake timers in Windows

Windows has a system-wide setting that controls whether timed tasks can wake compatible hardware. Open the active power plan's advanced settings, expand the sleep settings, and inspect Allow wake timers. Enable wake timers for the power state you use, such as plugged in. Laptop users should consider the battery impact before enabling them on battery power.

Also confirm that the task itself is configured to wake the computer. A Windows power setting cannot help if the AIMP task does not request a wake event.

Success means the PC wakes shortly before or at the test time and AIMP performs the action. Once that happens, do not change BIOS settings or reinstall audio drivers.

5.3 Understand sleep versus hibernation and shutdown

Wake support depends on hardware, firmware, the Windows power mode, and the task's configuration. A computer that can wake from ordinary sleep may not respond the same way from hibernation. A fully shut-down PC generally cannot depend on a running AIMP process to execute an AIMP task.

Test ordinary sleep first. Keep a laptop connected to power during diagnosis, because battery-saving policies can alter wake behavior. If sleep works but hibernation does not, use sleep for the alarm or investigate the computer manufacturer's supported wake capabilities.

Advanced users can run powercfg /waketimers in a Windows terminal to see whether an application has registered a wake timer. If no relevant timer appears after saving the task, recheck the wake option and task state.

6. Handle Android Sleep-Timer Problems Correctly

Current AIMP for Android documentation describes a sleep timer that stops playback at a specified time or playback boundary. It does not describe the full Windows Scheduler with recurring alarms, playlist-start automation, PC wake actions, or shutdown tasks. If you are looking for a recurring AIMP alarm on Android, the feature may simply not exist in the current mobile interface.

6.1 Test the Android sleep timer while the screen is on

Start a local track, set the sleep timer for a short interval, and keep AIMP in the foreground. Confirm whether playback stops at the chosen time or condition. If it does, the timer works and the later failure is likely connected to background or battery restrictions.

6.2 Check battery and background restrictions

Android can defer background activity and network access when a device is idle. Open the system's app information screen for AIMP and review its battery setting. If your device offers options such as Restricted, Optimized, or Unrestricted, test a less restrictive mode for AIMP. Menu names vary by manufacturer.

Also allow AIMP to display its playback notification and avoid force-stopping the application. A force-stopped app cannot be expected to continue normal background playback or timer behavior until it is opened again.

Success means the short timer works with the screen off and the device idle. Stop changing Android permissions after that result.

6.3 Verify storage and network access

If playback ends before the timer or cannot resume, confirm that AIMP retains access to the selected music folder. Regrant folder access through Android's system file picker when necessary. For Samba or other network playback, test with the screen off because Android power saving can interrupt network availability.

Use a local file for the timer test. If local playback works but a network stream fails, the timer itself is not the primary problem.

7. Run a Clean Temporary Test Before Reinstalling

A clean test is appropriate when the Scheduler interface is unavailable, its plugin repeatedly unloads, AIMP crashes after saving a task, or simple enabled tasks never execute despite correct power settings.

1. Back up playlists, presets, and other personal AIMP data.
2. Do not delete the existing profile.
3. Close AIMP completely.
4. Temporarily rename or move the profile folder so AIMP can create a fresh profile.
5. Start AIMP without adding custom skins or third-party plugins.
6. Create one playlist containing one known-good local file.
7. Create an enabled one-minute Scheduler task while the PC remains awake.

If the clean task works, the program installation and basic Scheduler components are functional. The problem is probably in the old profile, a saved Scheduler configuration, or an optional plugin. Restore data selectively rather than copying every settings file back at once.

If the clean test fails too, download AIMP only from its official website and consider a repair or clean reinstall after backing up your data. Record the exact error message, Windows version, AIMP version shown in the application, trigger type, and test result before asking for support.

8. Quick Fix Checklist

• Confirm that the Scheduler task is enabled.
• Set a one-minute time-triggered test using a known-good local file.
• Keep AIMP running instead of exiting it.
• Check that the next-run time is in the future.
• Verify the repeat days, interval, start date, and end condition.
• Confirm that the Scheduler plugin is installed and enabled.
• Test with the default skin and nonessential plugins disabled.
• Open the exact playlist, track, or stream manually.
• Choose an available audio output and check the Windows volume mixer.
• Enable the task's wake option and Windows wake timers for sleep testing.
• Test sleep before testing hibernation.
• On Android, distinguish the sleep timer from the Windows Scheduler.
• Review Android battery, notification, storage, and background settings.
• Use a temporary clean profile before reinstalling or deleting playlists.

9. Frequently Asked Questions

9.1 Does AIMP have to be running for Scheduler tasks?

Yes. AIMP Scheduler tasks are handled by AIMP, so the application must normally remain running. You can minimize it, but exiting the program removes the process that executes the task. Test this by confirming AIMP is present in Task Manager before the trigger time.

9.2 Why does the task work while Windows is awake but not asleep?

The task and source are probably valid, but the computer is not waking for the trigger. Enable the wake option in the AIMP task, allow wake timers in the active Windows power plan, and test ordinary sleep while connected to power. Hardware or firmware limitations can still affect hibernation wake behavior.

9.3 Why did an AIMP task run once and never repeat?

It may be configured as a one-time task, disabled after execution, limited by an end date, or set for different weekdays. Open the task and inspect its repeat rules and displayed next-run time. A correct recurring task should show another future occurrence.

9.4 Why does the alarm trigger without producing sound?

The selected playlist may be empty or inaccessible, the stream may be offline, AIMP may be muted, or playback may be routed to a disconnected USB or Bluetooth device. Test the exact source manually and switch temporarily to the Windows default output or built-in speakers.

9.5 Why is the Scheduler button gray or unavailable?

The Scheduler plugin may be missing, disabled, or unloaded after an error. Check AIMP's plugin settings. If the plugin repeatedly raises an exception, back up your data and run a clean-profile test rather than repeatedly forcing the component to reload.

9.6 Can AIMP for Android run the same recurring alarm tasks as Windows?

Current AIMP for Android materials describe a sleep timer, not the complete Windows-style Scheduler. Use the mobile sleep timer for stopping playback. For a recurring wake-up alarm on Android, use the operating system's alarm functionality or another appropriate alarm application.