If this has been happening for a few months it may be related to the bug in DTTG 3.5.7, which caused issues before Christmas, discussed in the forum (here, here). If that’s the case, I had it several times and running “verify and repair” on the affected databases and devices fixed the issue. It has not reappeared since so seems to have been thoroughly squashed.