Hi Matt & Brian, it was the magic of Kaseya Devs ;-) They are currently preparing a hotfix for this issue but in the meantime, they went ahead and fixed the issue directly in your systems.
Paul, if you ping me the ticket you submitted for this issue, I will get a dev to apply the fix, although as I said, a HF is in the making.
Thanks
- Amado.