Transfers
The Transfers page lists every check-in, upload and download between this machine and Prophouse. Transfers run in the local agent, not in the window, so they keep going when you close the window, and the queue is saved on disk so unfinished work continues the next time Prophouse runs.
The Transfers icon in the title bar shows how many transfers are in flight, or in red how many have failed. Click it to open this page.
Each row is one job: one check-in, one push from a tool or drop folder, or one download. A push of 500 files is one row, not 500.
Files saved with the Download button in the Cloud Library or on a detail page go straight to your download folder and don’t appear here. Downloads started from the Local Library, and the download that follows a check-out, do.
| Column | Shows |
|---|---|
| Job | The name of the item, or for a multi-item job the count and the first name (for example 12 items · SM_Crate and more), plus the number of batches and a short job id. |
| Type | Check-in, Download or Previews. |
| Status | Queued, In progress, Done, Failed or Cancelled, and how many batches failed if some did. |
| Progress | Items done out of the total, plus how many thumbnails and previews have uploaded alongside them. |
| Started and Duration | When the job started and how long it has run. Hover for the full timeline. |
Click the Job, Status, Progress, Started or Duration heading to sort by it. The page shows 50 jobs at a time.
Use the toolbar to narrow the list: search Search by name or job id…, pick a status, or choose Uploads or Downloads. Thumbnail and preview uploads that a push creates on its own are hidden by default; check Preview uploads to list them too. Export CSV saves the rows on the current page, and Refresh reloads the list.
Batches and items
Section titled “Batches and items”Click a job to open it. A large push is split into several batches because the server accepts a limited number of items per push; the job page lists them. The header shows Status, Type, Items, Batches, Preview uploads, Bytes, Started and Duration. Check Background uploads to include the thumbnail, preview and file uploads that belong to this job.
Click a batch to see every file in it, with its name, type, size and source path. Search with Search by name, path or hash….
Retry and cancel
Section titled “Retry and cancel”- Retry appears on failed jobs and failed batches. It puts the failed work back in the queue with a fresh set of attempts. On a job page, Retry failed items retries every failed batch at once.
- Cancel appears on downloads that are queued or in progress. On a job page, Cancel remaining cancels what’s left of a download job. A cancelled download keeps what it already fetched, so retrying it later resumes where it stopped.
Check-ins and pushes can’t be cancelled once queued; they are kept until they succeed or fail.
Sign-in problems
Section titled “Sign-in problems”If the server rejects the app’s sign-in, for example because the key was revoked or is read-only, affected transfers show Sign-in rejected and a banner explains that retrying won’t help. Click Sign in again with write access, approve the code in your browser, and the failed transfers retry automatically. See Sign in.
Other failures show the error under the status. Hover it for the full message.