Hi @arcus this error has been fixed in the VisualARQ 3.3 RC3 version we have published today: VisualARQ 3 - Version 3.3 RC3 released
Hi @arcus this error has been fixed in the VisualARQ 3.3 RC3 version we have published today: VisualARQ 3 - Version 3.3 RC3 released