My hotkeys stopped when my cloud drive went offline
The problem
My background scripts (hotkeys, backup jobs and file scans) were started from a cloud-synced folder. If the drive was unavailable at logon or at the scheduled time, they failed, and the PC had no offline copy to fall back on.
What I built
The live scripts now run from a local folder. The cloud copy became the deposit area where new working scripts land first. A repoint script made the switch: it does a dry run, takes backups before any change, and updates the startup shortcuts and scheduled tasks together. A short runbook records what runs where.
What changed
Hotkeys and backup jobs keep working offline, and there is one place to check what actually runs on the PC.
Tools
PowerShell, AutoHotkey v2, Task Scheduler, a cloud drive for archive and sync.
Who else would want this
Anyone whose automations live in a cloud-synced folder: homelabbers, small business owners and anyone who runs a backup script on a schedule. Cloud drives are great for syncing, but a script should not depend on one being reachable when it fires.
The rule I took from it
Keep the running copy local, and treat the cloud copy as the archive.