Manual runs work perfectly, but the scheduled run silently never happens. GoodSync scheduling almost never breaks — it just has quiet preconditions nobody told you about. Check them in this order.
✍️ Technical Anshu💻 GoodSync Auto Jobs⏱️ 15 minute diagnosis
🎥 The Auto settings are shown in the video — this guide adds the troubleshooting order for when the schedule does not fire
A scheduled backup that does not run is worse than no schedule at all, because you believe you are protected. The good news: in almost every case the cause is one of five ordinary things — the Auto setting was never actually saved for that job, GoodSync was not running at the scheduled moment, the PC was asleep, the destination path only exists for your logged-in session, or the job ran and failed and nobody read its log. Work through them in order and you will find yours.
GoodSync job log — the answer is usually sitting right here
Job: Nightly Office Backup
Last run: Yesterday, 20:00 - Completed with errors
ERROR: Right folder not accessible:
\\BACKUP-PC\OfficeData - network path not found
Job: Nightly Office Backup
Scheduled: Daily 20:00 (Auto: On Schedule)
Next run: Today, 20:00
👆 A job that DID run on schedule — and failed. The log names the exact reason. Half of all “schedule not working” reports are actually this screen, unread.
1
Fix 1 — Confirm Auto Is Really On, for This Job, and Saved
Auto settings in GoodSync are per job, not global. Setting a schedule on the test job does nothing for the real one.
Select the exact job in the job list, then open Job → Options → Auto
Check the mode is what you think it is — On Schedule with the right days and time, or Periodically with a sensible interval
Change anything small and click Save, so you know the settings were written
Sanity check the clock logic: a job set for 20:00 with the PC habitually shut down at 19:30 has a perfect schedule into a switched-off room
2
Fix 2 — GoodSync Must Be Running, or Running as a Service
The built-in scheduler lives inside GoodSync. If the application is fully closed at the scheduled time, there is nothing to fire the job.
On a personal PC: leave GoodSync running, minimized to the tray. Check its options to start with Windows so a reboot does not silently end your schedule
On a server or an office PC where people log off: jobs must run in unattended service mode — GoodSync's server component runs the jobs even when no user is logged in. This is the mode the business and Server editions are built for
Verify it: open services.msc and confirm the GoodSync server service exists and is Running with startup type Automatic
3
Fix 3 — The PC Was Asleep at the Scheduled Moment
A laptop on battery at 20:00 is very often asleep at 20:00 — and a sleeping PC runs nothing
Move the schedule to a time the machine is genuinely awake and plugged in — end of the working day beats the middle of the night on most office PCs
If the job must run at night, use Windows power settings and the Task Scheduler's wake options to wake the machine for it, and test once while watching
Also check the opposite failure: the job fired while the backup disk or NAS was asleep or off — the destination must be awake too
4
Fix 4 — The Destination Path Does Not Exist for the Scheduler
The classic service-mode trap: your job points at Z:\Backup, a mapped drive letter. Mapped letters belong to your interactive login session — the service running the job has no Z drive, so the path simply does not exist at 20:00.
Edit the job and replace mapped letters with the full UNC path: \\BACKUP-PC\OfficeData instead of Z:\
Make sure the account the service runs under actually has permission on that share — your own login working proves nothing about the service account
Cloud destinations have their own version of this: a sign-in token that expired while nobody watched. Open the destination once in the folder browser to refresh the connection
5
Fix 5 — Read the Job Log and Do One Watched Test Run
Select the job and open its log — GoodSync records every scheduled attempt, including the ones that failed in seconds. The error line tells you which of Fixes 1–4 you actually have
Fix that specific cause, then set the schedule five minutes in the future and watch it fire. A schedule you have never seen run is a hope, not a backup
Confirm the job ends with a clean result and the files really are on the destination — open the destination folder and look
Only now set the real time back. Total cost: ten minutes, once
🔴 The uncomfortable truth: most “GoodSync did not back up” stories are not scheduling bugs — they are laptops that were off, services that were never installed, or errors that sat unread in the log for weeks. After fixing yours, add one habit: glance at the job list once a week. Every job should show a recent successful run. The video shows where those statuses live.
🎥 Watch the Complete Video
See the Auto tab and the job statuses live in the video, so you know exactly which screens this guide is talking about.
My job says it ran, but no new files are on the backup disk. Why?
Usually the job ran against the wrong destination — a mapped letter that resolved somewhere else, an old job with a similar name, or a destination folder that was moved. Compare the exact Left and Right paths inside the job with the folder you are checking, and read the log line that lists how many files were actually copied.
Can GoodSync run a job when I am logged out of Windows?
Yes, but only in its unattended service mode — the GoodSync server component runs jobs in the background independent of any login session. A normal desktop install with the app closed will not run anything. Offices that log off at night should use the service mode and UNC paths, not mapped drive letters.
The schedule works for days, then stops after a Windows update or reboot. What changed?
A reboot closes the app and, if GoodSync is not set to start with Windows (or the service is set to Manual), the schedule quietly dies with it. Set GoodSync to start automatically, or set the service startup type to Automatic in services.msc, then test one reboot yourself so you know it survives.
This guide is based on the Technical Anshu GoodSync Explained video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏