Scheduled Jobs Done Right

The scheduler is the most trusted component in transfer automation — so trusted that nobody looks at it until a job silently stops running and three weeks of files fail to move. Task Scheduler and cron are both reliable tools with well-known sharp edges: environments that differ from your terminal, credentials that expire, reboots that eat run windows, and jobs that outlive everyone who remembers why they exist.

This series is about running the scheduling layer like it matters: Task Scheduler configured properly for transfer work, the real differences between cron and Task Scheduler, dedicated service accounts for jobs, what happens across reboots and missed windows, where scheduled jobs should keep their credentials, and the hygiene - naming, documentation, review - that keeps a schedule trustworthy for years.

Articles in This Series

• Windows Task Scheduler for Transfer Jobs, Properly
  A worked job setup: triggers and actions, run-whether-logged-on, the highest-privileges checkbox honestly, history and last-run results, and surfacing script exit codes so failures are visible.
• Cron and Task Scheduler Compared for Transfer Work
  Two mental models: environment handling, output and logging, missed-run behavior, credentials, and management at scale - plus sane conventions when you run both.
• Service Accounts for Scheduled Transfer Jobs
  Dedicated identities for automation: least privilege, no interactive logins, password and key handling, and making who-runs-this-job a question with a written answer.
• Jobs That Survive Reboots, Patches, and Missed Windows
  Missed-run policies - catch up or skip - startup ordering, dependencies on shares and VPNs that are not up yet, maintenance windows, and testing what your jobs do after a reboot.
• Where Scheduled Jobs Should Keep Their Credentials
  The stored-credential problem on both platforms: credential managers, key files and their permissions, keeping secrets out of repositories and backups, and rotation that does not break the schedule.
• Scheduled Job Hygiene: Naming, Docs, and Reviews
  Names that say what and why, descriptions that answer the questions successors ask, the jobs register, the periodic review that catches drift, and decommissioning without fear.

Explore More Topics

This series is part of the Sysax file transfer topic library, which covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build: Sysax Multi Server, a secure FTP, FTPS, SFTP, and HTTPS server for Windows, and Sysax FTP Automation, which schedules and scripts secure transfers so the routine ones run themselves.