A restore was being filed alongside scheduled backup and migration runs. It made the automation numbers on your dashboard read high — a workspace with a single job could show a month's worth of "automated runs" that were mostly recoveries and retries.

Restores now have their own category. They still appear in your activity feed and in analytics, where they're grouped as *Restores* rather than buried among scheduled work. If you're reviewing an account, the moments someone recovered data are now the easiest thing to find rather than the hardest.

"Automated runs" counts scheduled and manual job runs only, and the time-saved estimate beside it now counts only runs that actually copied something. A scheduled run that finds everything already in sync is still shown — that's your automation confirming it has nothing to do — but it no longer claims to have saved you work it didn't do.

We'd rather these numbers be smaller and true.