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 July 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. Each plan includes a set number of active jobs (see pricing).
#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.