Skip to content
Docs

How FileAgent runs

FileAgent runs as background services so the console and your scheduled jobs keep working without anyone signed in — even after a reboot.

Last updated July 17, 2026

#Two background services

FileAgent runs as two cooperating background services:

  • The web service hosts the browser console and its API.
  • The scheduler service wakes up on its own, checks which jobs are due, and runs them.

Separating them means your scheduled transfers keep running even when no administrator is signed in, and even if the console is briefly restarted.

#Always on, survives reboots

Both services start automatically when the host boots and continue running in the background. You don't need to keep a browser open or stay signed in for jobs to run. This is why FileAgent belongs on a machine that stays powered on — a host that sleeps or shuts down overnight will miss any jobs scheduled during that time.

#HTTPS-only console

The console is served over HTTPS only, reachable by hostname, IP address, or a DNS record pointed at the host. New installs generate a self-signed certificate; replace it with your own so administrators connect without warnings. See Certificates.

#Checking health

The System Status page (and the status indicator in the sidebar) reports overall application health, including whether the scheduler is running. Check it first whenever “jobs aren't running” — a stopped scheduler is the most common cause. See the Dashboard and service troubleshooting.