Getting Started#
Core Concept#
Set the Transfer Time and Recurrence to Automatically Run the Same File Task
When the same file transfer task needs to be run repeatedly, instead of selecting the Source and Target, checking files, and starting the transfer manually each time, you can configure the transfer task and execution schedule in advance so that it runs automatically at the scheduled time.
For example, you can configure daily reports to be transferred to a work server, materials to be sent to a remote system on a specific day each week, or backup files and archive data to be moved to storage according to a defined interval.
For a file transfer task, configure the Source and Target, file path, and transfer conditions, then use the Date/Time condition to separately specify when the task should start and how often it should repeat.
Schedule
│
┌─────────────┼─────────────┐
│ │ │
Daily Weekly Monthly
│ │ │
└─────────────┼─────────────┘
│
▼
Transfer Flow
┌─────┴─────┐
▼ ▼
Source TargetUnlike the Hot Folder method, which starts a task as soon as a file is created, scheduled transfer runs the specified file transfer task based on a predefined time and recurrence.
Therefore, it can be used in environments where tasks need to run according to business schedules or operational cycles rather than when files are created.
| Recurring Task | Scheduled Transfer Use |
|---|---|
| Daily Report | Transfer to the work server at a specified time every day |
| Weekly Materials | Transfer to the specified system on a specific day each week |
| Backup Files | Transfer to remote storage at a defined time or interval |
| Settlement Files | Automatically transfer at a configured time after the business day closes |
| Archive | Move specified files to long-term storage monthly |
For example, you can check and transfer report files from a specific path at the same time every day, or transfer materials generated during the week to a central system every Friday.
Scheduled Time
│
▼
Flow Starts
│
▼
Check Source Files
│
▼
File Transfer
│
▼
Check ResultThis configuration allows recurring file transfer tasks to run automatically instead of being started manually each time, following the sequence of set the execution schedule → start the Flow at the scheduled time → check Source files → transfer to the Target → check the execution result.
Scheduled Flow#
Check Files and Transfer Them Automatically When the Scheduled Time Arrives
When the scheduled time arrives, the configured transfer task starts automatically.
At execution time, the specified files are checked at the Source and transferred to the specified location on the Target according to the transfer conditions.
┌─────────────┐
│ Scheduled Time Reached │
└──────┬──────┘
▼
┌─────────────┐
│ Check Source │
└──────┬──────┘
▼
┌─────────────┐
│ Check Transfer Files │
└──────┬──────┘
▼
┌─────────────┐
│ File Transfer │
└──────┬──────┘
▼
┌─────────────┐
│ Reflect on Target │
└──────┬──────┘
Record Result
Record ResultBecause the schedule and transfer targets are configured in advance, files can be processed according to the defined flow without the operator having to start the task manually.
Automation Benefits#
Organize Recurring Execution and Transfer Time Management into a Single Schedule
When transfers are performed manually on a recurring basis, an operator may need to check files at the scheduled time and run the same transfer task each time.
With scheduled transfer, the execution time, target, and file path can be configured in advance to automate recurring work.
| Category | Manual Transfer | Scheduled Transfer |
|---|---|---|
| Execution Time | Checked manually by the operator | Runs automatically according to the configured schedule |
| Transfer Task | Started manually each time | Runs the same task repeatedly |
| Target Configuration | Checked each time the task runs | Target specified in advance |
| Recurring Management | Managed manually according to the work schedule | Managed automatically based on the schedule |
| Result Check | Check each task individually | Review based on execution records |
For example, different tasks can be operated on separate schedules as follows.
Every day 09:00 ─────► Daily Report ─────► Work Server
Every Friday ────────► Weekly Archive ───► Backup Storage
1st of every month ──► Monthly Data ─────► Cloud StorageThis allows recurring file work to be managed in a single flow from file preparation → scheduled time reached → automatic execution → target reflection → result check.
Teams#
Schedule Usage#
Set File Transfer Times to Match the Work Cycle
Teams can use configured transfer schedules for recurring file-related tasks.
For example, daily reports can be transferred before the workday begins, while weekly materials can be configured to transfer to another work environment on a specific day each week.
You can divide transfer schedules according to the work as follows.
| Work Cycle | Use Case |
|---|---|
| Daily | Transfer daily reports and work results |
| Weekly | Transfer weekly settlement materials and project materials |
| Monthly | Transfer monthly materials and archive files |
| Specific Day | Transfer files after a defined work deadline |
| Specific Time | Run at the start or end of the workday |
This allows file operations to be managed according to the defined work schedule rather than requiring users to remember when files need to be transferred.
Run Check#
Check Automatically Started Transfer Tasks and File Processing Results
When the scheduled time arrives, a new transfer task runs, and the team can check through the execution results whether the files were transferred successfully.
Repeated tasks can also be reviewed as individual execution records, making it possible to distinguish results executed on specific dates or at specific times.
Today's Scheduled Tasks
│
▼
┌─────────────────────┐
│ 09:00 Daily Report │
│ Completed │
├─────────────────────┤
│ 13:00 Backup Data │
│ Completed │
├─────────────────────┤
│ 18:00 Work Files │
│ Running │
└─────────────────────┘Execution results provide the following information.
Scheduled transfer task
Actual execution time
Current progress status
Number of files transferred
Total transfer size
Transfer completion time
Target reflection result
Total transfer size When the transfer is complete, check the files on the target system and continue with the next task.
Transfer completion time
IT Engineer#
Schedule Setup#
Configure the Execution Cycle and Time of Transfer Tasks to Match the Work Requirements
IT engineers configure the date and time for automatic execution through the Date/Time condition after setting up the file transfer task.
You can configure tasks to run at the same time every day or repeatedly according to a specific day of the week or work cycle.
Transfer Flow
▲
│
┌───────┴───────┐
│ Schedule │
├───────────────┤
│ Daily 09:00 │
│ Weekly Mon │
│ Monthly 01 │
└───────────────┘When setting a schedule, execution criteria can be separated according to the characteristics of the transfer task.
| Configuration Criterion | Configuration Method |
|---|---|
| Execution Cycle | Set recurrence by day, week, or month |
| Execution Time | Specify according to the start or end of the workday |
| Execution Day | Run the task only on specific days |
| Target Files | Specify the Source path to check at execution time |
| Target Location | Specify the file storage location on the Target |
By configuring the schedule together with the transfer path, the same transfer task can be run repeatedly at the scheduled time.
File Criteria#
Configure Processing Criteria to Transfer Only the Required Files on Each Recurring Run
Even when the same transfer task runs repeatedly, it is not necessary to process every file in exactly the same way each time.
You can use conditions such as file paths, names, and extensions to configure the task to transfer only the files required for that schedule.
Source Folder
│
├── report_0901.csv
├── report_0902.csv ◄── Process today
├── backup_0902.zip ◄── Matches condition
├── temp.log ─── Excluded
│
▼
Scheduled Transfer
│
▼
TargetTransfer criteria can be configured according to the characteristics of the work.
| Criterion | Use |
|---|---|
| File Path | Check only the specified work folder |
| File Name | Select targets according to date or work-name rules |
| Extension | Transfer only the required file types |
| Modification Status | Process newly created or modified files |
| Duplicate Status | Manage duplicate transfers of files processed previously |
This allows the transfer flow to be configured based on the files actually required each time the recurring task runs.
Job Configuration#
Connect Multiple Transfer Tasks in Sequence Within a Single Schedule
Recurring transfer can connect multiple tasks to a single schedule, rather than simply sending one file to one Target.
For example, you can configure the system to first transfer backup files to remote storage every morning, then send them to another archive environment after completion.
Every Day 02:00
│
▼
Backup Transfer
│
Completed?
┌────┴────┐
Yes No
│ │
▼ ▼
Archive Storage Check Required
│
▼
Result Recorded[
This configuration allows a single execution schedule to automatically process transfer → completion check → next transfer or follow-up task in sequence.
Run Management#
Distinguish and Review Recurring Tasks by Schedule and Run Records
Each time a scheduled transfer task runs, it is recorded as a new Run.
IT engineers can check whether a specific transfer task ran according to the planned schedule and compare results across executions.
| Check Item | Details |
|---|---|
| Schedule | Configured recurring schedule |
| Started | Actual task start time |
| Source | Device and path where files were checked |
| Target | Target environment where files were reflected |
| Total Files | Number of files processed in the execution |
| Total Size | Transfer size for the execution |
| Status | Completed, in progress, or review required |
| Completed | Actual completion time |
For example, if a task did not run on a specific date or its processing result differs, you can check the Source and Target status based on that Run.
Exception Handling#
Check When a Scheduled Task Does Not Run or File Processing Encounters a Problem
In a recurring transfer environment, the scheduled time may arrive while the Source device is inaccessible, the target files are not ready, or there is a problem with the Target connection.
In this case, reviewing the execution record in the order of schedule → Source → files → Target helps identify where the problem occurred.
Scheduled Run
│
▼
┌───────────────┐
│ Check Execution Result │
└───────┬───────┘
│
┌────────┼────────┐
▼ ▼ ▼
Schedule Source Target
│ │ │
└────────┼────────┘
▼
Check Settings
│
▼
Adjust Required Environment
│
▼
Retry
│
▼
Check New RunIf a problem occurs, you can check the following items together.
| Check Item | Details | Response |
|---|---|---|
| Execution Schedule | Configured date and time | Check Schedule settings |
| Source Connection | Access status of the source device | Check the device connection |
| File Status | Whether the transfer target file exists | Check the file path and preparation status |
| File Conditions | Filters and processing criteria | Adjust the condition settings |
| Target Connection | Access status of the target system | Check the storage location and access scope |
| Execution History | Processing results for each Run | Rerun the required task |
This configuration goes beyond simply running recurring file transfers automatically and enables a single operational flow covering schedule setup → file check → automatic transfer → execution records → exception review.