Transfer Engine
What this section does
Section titled “What this section does”This chapter explains the run lifecycle, file safety behavior, cancellation handling, and outcome reporting.
Run phases
Section titled “Run phases”- Validation: Checks enabled rule completeness before touching files.
- Volume resolution: Enumerates mounted volumes and resolves selected sources.
- File count scan: Counts eligible files to set progress totals.
- Transfer loop: Processes matching files one at a time.
- Summary: Aggregates completed count, errors, and notices.
File transfer behavior
Section titled “File transfer behavior”Copy action
Section titled “Copy action”- Copies file to destination.
- Source remains unchanged.
Transfer action
Section titled “Transfer action”- Copies file to destination.
- Computes SHA-256 on source and destination copy.
- Deletes source only when hashes match.
- Keeps source when hashes do not match and logs an error.
Naming conflicts
Section titled “Naming conflicts”When destination filename already exists, app adds numeric suffix (example: IMG_0042-1.jpg).
Cancellation
Section titled “Cancellation”- Triggered by Stop button or
Command + .shortcut. - Current task is cancelled.
- Already completed items remain counted in summary.
Outcome model
Section titled “Outcome model”- RuleRunOutcome: per rule/volume completed files, errors, notices.
- IngestAggregate: merged totals from all rule/volume runs.
- IngestSummary: final status (
completed,completedWithErrors,cancelled) and detail lines.
Log output
Section titled “Log output”When log saving is enabled, each run writes a .txt log with:
- run timestamp,
- status,
- completed count,
- error count,
- notice count,
- full detail lines.
Known limitations
Section titled “Known limitations”- No content-hash dedupe before transfer.
- Source subfolder tree is not preserved (destination is flat).
- Scan totals can differ if source changes during run.
- Keep source media static while a run is active for the most accurate totals.
- Use Transfer mode only after destination validation.
Are “no matching files” treated as failures?
Section titled “Are “no matching files” treated as failures?”No. They are recorded as notices and the run continues.
Can partial completion happen on cancel?
Section titled “Can partial completion happen on cancel?”Yes. Completed files before cancellation remain completed.
Related guides
Section titled “Related guides”Need help?
Section titled “Need help?”For setup support, contact rockstarui.com/contact.