Creating a job
Walk through building a transfer job from scratch — name it, choose source and destination, pick a mode, and validate it with a manual run before scheduling.
Last updated July 17, 2026
#Before you begin
- Create and test the credentials the job will use (local folders need none).
- Know the exact source and destination paths, and which files you want.
- Have a safe scratch destination ready for the first test run.
#Create the job
- Go to Jobs → New job.
- Give it an operational name, like
Nightly reports → S3. - Pick the source: connector type, credential (if needed), and path.
- Pick the destination the same way.
- Choose the transfer mode — start with Copy (see Transfer modes).
- Optionally set a file pattern to limit which files are included.
- Leave the schedule off for now and save.
#Test before you schedule
- Use Run now and open the run in Logs.
- Confirm the expected files were selected — the expected count and size.
- Point at the real destination, run again, and verify end-to-end.
- Only then switch to Move or Sync/Mirror if needed, and enable the schedule.
Start with Copy into an empty test destination. Once the file selection is what you expect, switch to the mode you actually need.
#Finish setup
With the job validated, add failure alerts, enable archiving if it moves files, and set retries and conflict handling for production reliability.