First a little background: I recently ran into an issue in Veeam Backup & Replication where a backup set would fail to be imported into the console under 'Disk (encrypted)' after rescanning the cloud connect repository.
When rescanning the repository Veeam would see the new data but it would never show up in the console. After opening a case with support it was determined that the reason the data wouldn't show up in the console was because the backup set was corrupted. Veeam was silently failing the import and the only way we determined what had happened was to dig into the application logs.
My request is this: when this sort of scenario happens Veeam should notify the user in some manner, probably in the repository scan window, that the backup cannot be imported due to 'x' so we know if we need to try re-uploading the data or re-seeding the job.