We've been performing some Hub maintenance these last couple of days, so the TKLBAM/Hub cache sync was probably not being triggered. The way it works is as a backup is completed, TKLBAM sends a trigger to the Hub to update its cache. Due to the maintenance the trigger was probably not being handled.
Just to be clear, there is no need for concern. If the TKLBAM backup completed successfully then the backup itself was successfull. The Hub's cache is just probably out of date. Once the issue resolved all backup sessions will be displayed.
No need for concern...
We've been performing some Hub maintenance these last couple of days, so the TKLBAM/Hub cache sync was probably not being triggered. The way it works is as a backup is completed, TKLBAM sends a trigger to the Hub to update its cache. Due to the maintenance the trigger was probably not being handled.
Just to be clear, there is no need for concern. If the TKLBAM backup completed successfully then the backup itself was successfull. The Hub's cache is just probably out of date. Once the issue resolved all backup sessions will be displayed.
Sorry for the late reply and reporting the issue!