check / check (push) Waiting to run
Once a worker has thrown, as one does when onProgress throws, or the lock is lost, no worker takes another file, and the backup fails once the originals under way are in place. Before, the other workers went on through the rest of the account after a throw. Once the workers have stopped, the backup checks its lock, so a lost lock no longer lets it start the ML data fetch. The end-to-end test's comment now says the backup has started all three originals when the lock is lost, not that all three are still downloading. Model: opus-5-5