Jobs

Where to find it

While jobs run, Jobs shows a spinner and how many are running, and it adds a red count when a job has failed.

What becomes a job

Copies, moves, uploads, downloads, renames and deletes in the Files workspace run as jobs, as do bucket backups, emptying a bucket, snapshots, exports and imports. Transfers an agent starts through agent access appear in the same list. The popover, titled Data transfers, keeps up to 20 finished jobs beside the running ones. Counting a bucket and previewing a backup stay inside their own dialogs.

States and badges

A running row shows a spinner, a progress line where the total is known, and a stop button. A finished row shows a green check, a cancelled row reads Cancelled with how far it got, and a failed row shows its error in red. A transfer between two connections carries SERVER when the work runs on the server and VIA APP when the data passes through this computer, and pointing at the badge explains it. A backup that stopped early offers Resume in Backups.

Cancelling

Press the stop button and the row reads Cancelling until the job has reached a safe point and ended. A transfer keeps the objects that had fully arrived, removes the partial file of anything it was writing, and on a move deletes nothing from the source. A snapshot or export removes its unfinished file and ends its database work, a delete stops between batches, and emptying a bucket lets the delete batches already sent finish. A cancelled backup keeps its place and can be resumed from Backups.

After a job

A finished snapshot offers Reveal, which shows the file in your file manager or opens its folder on a file connection, and Copy restore command. The close button removes one finished row, and Clear finished removes every row that is not still running. Finished rows are not kept when the app restarts.

Failures

A failed row stays until you remove it, and Jobs counts it in red. For a transfer, the error says how many items failed, names up to 20 of them and gives the first error; point at the line to read all of it. Transfers have no retry, so fix the cause and start the transfer again. A failed snapshot offers Retry, and a purge that left keys behind offers Show failures.

Good to know

• The list belongs to the window, so switching workspaces or tabs in that window neither hides nor stops a job.
• Quitting the app does not ask about running jobs and stops them where they are. Start transfers again afterwards, and resume an interrupted backup from Backups.
• A PostgreSQL export streamed with COPY shows a COPY badge.
• Sizes in job rows use decimal units, so 1 MB is 1,000,000 bytes.