Jobs overview
A job is a saved transfer definition — a source, a destination, a mode, a schedule, and reliability settings. The scheduler runs enabled jobs on time; you can run any job on demand.
Last updated September 17, 2026
#What a job is
A job is a saved transfer definition: a source, a destination, a transfer mode, an optional schedule, and reliability settings. The scheduler runs enabled jobs at their scheduled times, and you can run any job on demand. Every execution is recorded as a run with its status, duration, and file detail.
Jobs are managed under Jobs in the sidebar. Plans limit how many jobs can be active at once: 2 active jobs on Free, 25 active jobs on Pro, 100 active jobs on Business, custom active jobs on Enterprise.
- Active job
- An enabled job definition that can run on its schedule or manually, including Scheduled Purge jobs. Repeated runs of the same job do not use additional slots. Disabled jobs do not count, but a disabled job must fit within your active job limit before it can run.
Enabling a job, running a disabled job with Run now, cloning or importing an enabled job, and job changes made through the AI Assistant all check the limit first. If a plan change leaves more enabled jobs than the plan allows, nothing is deleted: the jobs that fit keep running and the rest wait until you disable jobs or upgrade.
#The parts of a job
| Part | What it controls |
|---|---|
| Name & tags | How you find and organize the job. |
| Source | Where files come from — connector, credential, and path. |
| Destination | Where files go — connector, credential, and path. |
| Transfer mode | Copy, Move, or Sync/Mirror (or a Scheduled Purge). |
| File pattern & filters | Which files are included. |
| Schedule | When it runs automatically. |
| Reliability | Conflict handling, retries, and timeouts. |
| Archive & alerts | Recoverable copies of moved files, and notifications. |
#The job lifecycle
- Create the job and point it at a source and destination.
- Run it now to confirm it does what you expect.
- Schedule it and add alerts.
- Review runs in the logs and adjust as needed.
- Edit, disable, or delete it as your workflows change.
#Best practices
- Name jobs operationally (
AP exports → vendor SFTP), not generically (Job 7). - One purpose per job — several small jobs beat one giant job: clearer logs, safer retries, independent schedules.
- Use Move + Archive for pickup folders so processed files can't be picked up twice and can always be recovered.
- Add failure alerts to every production job.
- Review the logs weekly for partial-success runs and unexpected “no files” results.