feature/windows-start-when-available

[hollowhemlock]

Feature Request: Add schedule-start-when-available option for Windows Task Scheduler

Problem

When a scheduled backup is missed because the computer was asleep, off, or otherwise unavailable, Windows Task Scheduler does not run the task by default. This means backups can be silently skipped if the machine isn't running at the exact scheduled time.

Proposed Solution

Add a new schedule-start-when-available option (and the corresponding start-when-available in schedule blocks) that enables the Windows Task Scheduler "Start the task as soon as possible after a scheduled start is missed" setting.

Example Configuration

profile:
  backup:
    schedule: "03:00"
    schedule-start-when-available: true

Use Case

Laptop users who may close their laptop or put it to sleep before a scheduled backup
Desktops that may be powered off overnight
Any scenario where the machine might not be running at the scheduled time

Possible Issues

Conflicts with overlapping schedules.

Platform

Windows only (Task Scheduler feature)

###Related
Similar to the existing schedule-ignore-on-battery option which also controls Task Scheduler behavior

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• [feature] Runlevel option for schedule on Windows #475
• Windows 11 hide backup window when backup runs as Windows Task for non-admin user #474
• Resticprofile fails to add a scheduled task in Windows 11 #481

👤 Suggested Assignees

• auxym
• languagegame
• TopazYC

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[ekcom]

Duplicate of #303 (but more detailed here)