Add an option to allow scheduled tasks in Lenovo Legion Toolkit to run if they were missed (e.g., because the laptop was off or asleep at the scheduled time).

[Eagle10021]

Version

2.25.3

OS

Windows 11 23H2 22631.5189

Device

Legion 5 15ACH6H

Is your feature request related to a problem?

Yes — currently, scheduled tasks (like keyboard backlight changes) do not run if the laptop is powered off, sleeping, or restarting when the scheduled time hits. As a result, automations silently fail and do not trigger later when the laptop is back on.

How would you like the problem to be solved?

Add an option to scheduled automations that allows them to run if missed, ideally right after the system boots or wakes from sleep. This would ensure that time-based tasks still run once, even if the system wasn't active at the exact time they were scheduled.

Example: If I schedule a keyboard backlight change at 6:00 PM, but my laptop is off, the task should run once when I turn it back on (e.g., 6:20 PM), then return to normal schedule afterward.

Checkbox name suggestion:
☑ “Run this task if it was missed (on next startup/logon)”

What alternatives have you considered?

I’ve considered using Windows Task Scheduler to run a custom script that applies the same setting on boot. However, this adds complexity and defeats the simplicity of using Lenovo Legion Toolkit's built-in automation. A built-in option would be more user-friendly and consistent.

Additional information

This would be particularly helpful for users who frequently suspend or reboot their laptops and rely on automation for things like:

Keyboard backlight presets

Fan/power profiles

GPU switching

Would also be great if the “missed task window” was configurable (e.g., “run if missed within the last X minutes”).

[BartoszCichecki]

Currently there is no way to achieve what you describe.

Actions are based on events and there is no way to keep track of what events happened during sleep or powered off state. It also isn't tracked which Actions already ran.

Looking at your example:

I have an action configured to run at 8pm. I put my laptop to sleep at 7pm. And I wake it up at 9pm.

You could say to just run the action scheduled for 8pm. But what if I wake the laptop again at 10pm? What then? LLT doesn't keep track of Actions that were already ran. Running the action again isn't an option and introduced a whole different level of complexity.

The missed task window you describe, maybe could somehow work for time triggers, but is impossible to implement for other actions.

Your idea is valid, but giving that Actions are purely based on events, I don't really see a way to make it work. As you said, the simplicity of actions in LLT is what makes it easy to use. And unless we can make a bullet proof plan here, your option is to resort to scripting and using CLI that LLT exposes, to create more custom and complex solutions.