@SpeedMan - I have successfully managed to reproduce this error using 2 methods.
This method is cheating, but...: I used Kodi v20.5 in a virtual machine communicating to TVH on a physical machine. Using the hypervisor to suspend the whole VM, I could reproduce the error in Kodi when the VM was restarted.
In the same VM, I used the 'Suspend' feature from the Kodi power menu to put the VM into hibernate/sleep. I then deleted a recording on the physical TVH machine. Once I restarted Kodi, the deleted recording was still visible.
I also saw that when I started a new recording on the physical TVH box, the new recordings showed up in Kodi, but the 'deleted' recordings also remained in the list. A little creepy, but expected.
After a full reboot of the Kodi VM, the 'deleted' recordings were gone.
I also experimented with scheduling a recording whilst Kodi was suspended and this turned up immediately when Kodi woke up. The 'deleted' recordings, however, where still present in Kodi. I also tested suspending Kodi when a recording is in progress and then cancelling the recording whilst the Kodi VM was suspended. The recording that was in progress immediately showed as being complete when the Kodi VM restarted.
This is not absolute proof, but it is strongly supportive. I'd like to test on the latest version of Kodi as well as 2 physical machines. Unfortunately, I don't have a spare physical machine that I can easily nuke and install the latest Kodi on.
