Scheduler (Pro): In‑App Scheduling vs Windows Task Bundle

Two scheduling models exist for enterprise practicality:

1) In‑App Scheduler
- Runs only while the app is open.
- Best for personal or always‑on “QA workstation” setups.

2) Windows Task Bundle (portable)
- Exports a standalone folder that can run without the desktop UI.
- Intended for:
  - machines where the app is not running
  - dedicated runner VMs
  - copying to another machine

What the Windows bundle should contain
- A portable workspace subset for the selected schedule:
  - project
  - selected suites
  - tools (including wsq-cli.jar)
  - config needed to run
- All reports/history written INSIDE that bundle’s workspace.

Operational notes
- One task per schedule entry.
- If overlap is detected (same machine), the runner should skip or lock.
- Jobs marked source=WINDOWS should be displayed in the Windows list (not mixed into app jobs).

If the bundle folder is empty
- That is a bug. The export action must copy artifacts.
- Confirm you selected:
  - Project
  - One or more suites
  - Output folder
  - And then Export

Use the Intelligent Assistant for guided troubleshooting and next actions.