Repository navigation
Help dock repo_sync_queue
Repository Sync Queue shows prepared file transfers between configured repositories and the local workstation, including progress, conflicts, cancellation and retry.
Every row retains the source file object's identity, repository, path and intended destination. Discovery can add many files, but transfer starts only for explicit queue operations.
The queue reports waiting, running, completed, cancelled and failed states, transferred bytes and an actionable error. Removing a queued row does not delete its source or an already completed local file.
- Start or pause eligible queue work.
- Cancel an active or waiting transfer.
- Retry a failed item after correcting its cause.
- Remove completed or unwanted rows.
- Open the Repository Sync window to discover and prepare a broader scope.
Existing destination files follow the chosen conflict policy; they are never overwritten merely because a row appeared in the queue. Snapshot metadata helps discovery, while completed HTTP transfers are verified against response metadata.
- Prepare files from Snapshot Browser or Repository Sync.
- Review source repository and local destination.
- Resolve conflict choices before starting.
- Watch per-file and total progress.
- Retry only after repository, path, permission or connection errors are corrected.
- A missing or unavailable local repository keeps the row waiting without repeated error notifications. Apply a usable path in Repository Editor to resume it.
- Cancellation is a normal terminal state, not an application error.
- A temporary network failure keeps the source identity for retry.
- Credentials and tokens never appear in the visible detail or Debug Log.
Create and save stores the selected process tree as a server preset. Save updates the selected preset; it does not create a second record. Delete asks for confirmation and removes that preset. Partial scope and chunk size control the current run and are not written into the preset's process tree.
Selected child types (for example Texture) include their linked records and the checked processes below them. Discovery must finish successfully before these files reach the queue; an earlier completed download does not mean discovery succeeded. After a discovery error, correct its cause and start Repository Sync again.
TACTIC-Handler · Releases · Issues · English · Русский
English
- Home
- Installation
- Feature tour
- User guide
- Assistant
- Dashboards
- Knowledge Base
- Maya / Shelf
- Plugins / Плагины
Русский
- Главная
- Установка
- Обзор возможностей
- Руководство пользователя
- Помощник
- Дашборды
- База знаний
- Maya / Shelf
- Plugins / Плагины
Development / Разработка