A migration that hit an unreadable file could sit at running, 100% until the 24-hour reaper stopped it. The underlying cause was an error that our SSH library reports on the connection rather than on the file's stream, where nothing was listening — the transfer then waited forever on a source that would never speak again. Those files now fail as ordinary per-file errors and the run completes with them listed.

Also in this release:

• •The progress bar counts files that are finished, not files that have been picked up, so it no longer reads 100% while the last few are still transferring.
• •The job detail page polls while a run is queued or running — the status and log used to freeze until you reloaded the page.
• •Opening a job from the Jobs table used to be able to show you a different job: backup and migration ids are issued independently, so the two could collide. Links now carry the job's kind.
• •Delete is available on the Jobs table and on the job detail page, not only on the job cards.
• •The thread count, schedule, source server, paths and destination of a migration job are all editable now. Previously changing where a job pointed meant deleting it and building it again.