Phew! Yeah, the same files are always the last to catch up. Though once I see “Items pending backup” down to under 10-20 I know it’s on the home stretch.
Hmm. It looks to me though the backup should be almost finished by now. What’s the “Samples pending backup” down to now?
Aside: One thing that can happen with the scheduled background tasks is that iOS will start the task, then “expire” only a few seconds after, deciding that it doesn’t want to let the app finish doing the task to completion.
Arc can’t immediately stop what it’s doing - the various tasks get broken up into batches of work and it can only stop between batches. So once Arc gets told the task has expired (and is required by iOS to stop doing any more of it) it still finishes up the current batch of work. If there was only one batch of work to be done, then technically the job will be complete, even though iOS marked it as expired. So it can end up showing as incomplete even though all the work was finished.
That is very common with the coreMLModelUpdates task you see in the list. iOS almost always expires that task only seconds after starting it (super annoying!). But often that task only had one thing to do, so it’ll still end up having finished all of its work, even though it says “overdue by 19 days”.
The same can happen with the backups task. Although that’s much less common. So typically when the backups task says it’s overdue by X days, that’s usually correct, in the sense that it hasn’t managed to fully finish the job in that many days. Although the actual data in the backup might be almost up to date - it just hasn’t been given a chance to fully finish the job in that many days.
I think it’s best to wait. Or at least, wait until “Samples pending backup” is down really low. Like, maybe once it’s under 10,000 or so. Or if it says it’s actually completed the backups in the last day.