lwolfAn update.... my problem is now corrected.
Per an email message from Ypovanni in Kaseya Support:
There was a database change that I did to correct the issue. We have had a couple of other customers experience the same issue and that change corrected them.
Thank you for contacting Kaseya Support
Here is another thread with the same info