Skip to main content
After a batch is saved, open Transfers in the manager to see its jobs. The queue records source download, upload and metadata publication separately. Your browser profile keeps the jobs locally so closing a manager tab does not erase the recorded queue.

Understand completion

The progress bar can show all upload bytes sent while metadata is still being saved. Studio thumbnail processing can finish after the transfer is done. For example, a tag-permission failure after upload leaves the file in Studio and the queue records the metadata error. Retry continues the existing job’s metadata step.

Pause, resume and cancel

Use a job’s Pause, Resume, Retry or Cancel control. Queue-level Pause and Resume apply to unfinished jobs. Clear finished removes completed and cancelled local history and its retained job blobs. It preserves accepted Studio assets. Cancellation aborts the active local request and attempts to cancel a recorded server upload session. A file already accepted by Studio can remain there. Inspect the destination and use Studio’s trash workflow if you also want to remove that asset.

Ordinary and resumable uploads

Studio publishes small files through the ordinary upload endpoint. When resumable sessions are enabled and the file exceeds the selected threshold, the extension records a session and uploads parts through the application. A resumed session reads accepted parts and skips those already stored. The extension requests direct: false. It can save to a workspace backed by S3 while the transfer passes through Laravel. Enabling direct S3 on the host does not switch the current extension queue to signed S3 part PUTs. Server upload configuration The job retains its upload key and accepted entry identity. Retry the existing job for an interrupted transfer. Starting a new capture creates new queue jobs and new operation keys.

Automatic recovery and limits

Network errors, rate limits and server failures can be retried automatically. The queue uses an increasing delay and stops automatic retrying after four failed attempts. Manual Retry resets the attempt counter. Authorization and validation responses generally need a correction before retrying. A background alarm checks the queue, and stale active jobs can be returned to queued after interruption. Progress depends on the browser running and allowing extension background work. If a recorded session expires before resumption, cancel that job and recollect the file to start a new session. Queue admission also applies a 256 MiB budget based on job sizes already known at admission. Newly discovered remote sizes can require capacity checks later when bytes are stored. Finish jobs and clear completed history before starting another large batch.

Troubleshooting

Browser storage can also be removed by clearing extension data or uninstalling the extension. Verify that required files are present in Studio before removing that local state.