The clue is in your own observation: re-enabling the disabled manual job made all VMs appear. The Backup Restore (V5) view likely filters its restore list based on which backup jobs are currently enabled, if a job is disabled, its associated VMs may not be indexed into the restore view even if backups from that job exist on the remote.
This is different from how the older restore view worked, where it would scan the remote and show everything regardless of job state. The V5 restore view appears to be building its list from job metadata rather than from a direct remote scan.
A few things worth verifying:
Check whether the one VM that does appear is covered by a currently-enabled job, and the others are only covered by disabled jobs. If that pattern holds consistently, that's the root cause and it's a V5 behavior change worth reporting to the XO team. In the XO UI, go to Backup → Jobs and check which jobs are enabled. If you temporarily enable all jobs, does the restore list show all VMs? And when you disable some again, does it immediately drop those VMs from the list?
If the behavior is confirmed, filing it against the backup v5 restore view filter logic would be useful, the restore UI should show all VMs that have restorable backups on the remote, regardless of whether the originating job is currently active or not.
Given you're on a test branch focused on reactivity fixes, this could also be a rendering/state issue where the component isn't re-fetching when job state changes, the list gets built once and doesn't update until you navigate away and back.
